On Tuesday 21 July 2009 5:49:16 am Thiago Macieira wrote:
> Em Segunda-feira 17 Setembro 2007, às 21:02:25, Thiago Macieira escreveu:
> > I'd like to welcome everyone. This mailing list is to discuss a new
> > Source Control Management tool for KDE. It is not tied to a particular
> > tool, though I
On Tue, Jul 21, 2009 at 6:29 PM, Chani wrote:
> i miss kmail already :P got the list addy wrong this time
>
> On 7/21/09, Chani wrote:
>> oops, it seems google sent my last email to chusslove instead of to the list.
>>
>> anyways... i was about halfway through a patch when they came to take
>> m
i miss kmail already :P got the list addy wrong this time
On 7/21/09, Chani wrote:
> oops, it seems google sent my last email to chusslove instead of to the list.
>
> anyways... i was about halfway through a patch when they came to take
> my laptop. sorry.
> it seemed like a fairly simple patc
>> [: Chusslove Illich :]
>> [...] l10n-kde4/templates/messages/amarok/ and the four of Amarok's POTs
>> inside?
>
> [: Chani :]
> I assume so. after all, amarok won't physically be in extragear, at least
> while it's being a guinea pig. is there a problem with that?
I would say that's a problem.
On Tuesday 21 July 2009 13:42:27 Jeff Mitchell wrote:
> The #2 you saw (and #3 about one branch per bugfix/feature) is more
> applicable to a random one-off patch contributor who won't be added to
> the kde-developers group. They should clone the repo, create a branch
> per bugfix/feature, and then
On July 21, 2009 09:00:45 Ian Monroe wrote:
> 2009/7/21 Chani :
> > On July 21, 2009 04:39:27 Chusslove Illich wrote:
> >> > [: Chani :]
> >> > a) add your module to the list in list_modules (you guys were part of
> >> > extragear-multimedia, but now you're your own module)
> >>
> >> Does this mean
2009/7/21 Chani :
> On July 21, 2009 04:39:27 Chusslove Illich wrote:
>> > [: Chani :]
>> > a) add your module to the list in list_modules (you guys were part of
>> > extragear-multimedia, but now you're your own module)
>>
>> Does this mean that, if everything goes according to plan, we are going
On July 21, 2009 04:39:27 Chusslove Illich wrote:
> > [: Chani :]
> > a) add your module to the list in list_modules (you guys were part of
> > extragear-multimedia, but now you're your own module)
>
> Does this mean that, if everything goes according to plan, we are going to
> end up with e.g. l10
Em Segunda-feira 17 Setembro 2007, às 21:02:25, Thiago Macieira escreveu:
> I'd like to welcome everyone. This mailing list is to discuss a new Source
> Control Management tool for KDE. It is not tied to a particular tool,
> though I suspect one will dominate the emails.
>
> You may discuss any SCM
Thomas Zander wrote:
> On Tuesday 21 July 2009 13:24:18 Riccardo Iaconelli wrote:
>> Hmm... I'm a bit scared of using this approach, where you don't share the
>> work directly in the mainline repo, but instead work on your own clones. I
>> mean, while being very git-ish, aren't we losing here the s
> [: Chani :]
> a) add your module to the list in list_modules (you guys were part of
> extragear-multimedia, but now you're your own module)
Does this mean that, if everything goes according to plan, we are going to
end up with e.g. l10n-kde4/templates/messages/amarok/ and the four of
Amarok's PO
On Tuesday 21 July 2009 13:24:18 Riccardo Iaconelli wrote:
> Hmm... I'm a bit scared of using this approach, where you don't share the
> work directly in the mainline repo, but instead work on your own clones. I
> mean, while being very git-ish, aren't we losing here the social model that
> we all
Riccardo Iaconelli schrieb:
> On Monday 20 July 2009 10:49:24 Bart Cerneels wrote:
>>> 1) Never, ever create a branch in our mainline repo. Ever. You can do it
>>> locally, but do not push it up.
>>> 2) Clone the repo and work on that. Add mainline as a remote branch in
>>> your local copy of your
On Tue, Jul 21, 2009 at 10:24 AM, Riccardo Iaconelli wrote:
> On Monday 20 July 2009 10:49:24 Bart Cerneels wrote:
>> > 1) Never, ever create a branch in our mainline repo. Ever. You can do it
>> > locally, but do not push it up.
>> > 2) Clone the repo and work on that. Add mainline as a remote bra
On Monday 20 July 2009 10:49:24 Bart Cerneels wrote:
> > 1) Never, ever create a branch in our mainline repo. Ever. You can do it
> > locally, but do not push it up.
> > 2) Clone the repo and work on that. Add mainline as a remote branch in
> > your local copy of your cloned repo.
Hmm... I'm a bit
15 matches
Mail list logo
