Michael Pyne schrieb:
> Do you bypass the guy who reviews your patches and instead submit it to
> the next higher guy? (Hint: NO, unless you've already cleared such behavior)
>
> What happens if someone in the chain becomes unavailable due to other
> more important committments (after all, the pro
On Monday 19 January 2009, Johannes Sixt wrote:
> Ian Monroe schrieb:
> > On Sat, Jan 17, 2009 at 5:17 PM, Thiago Macieira wrote:
> >> * should we use a patch-submission-and-review system? (probably not)
> >
> > no.
>
> Don't throw patch submission and review into the same bucket. I can
> underst
Robert Wohlrab wrote:
>On Monday 19 January 2009 19:44:33 Oswald Buddenhagen wrote:
>> On Sun, Jan 18, 2009 at 06:45:47PM +0100, Thiago Macieira wrote:
>> > git.kde.org:kdelibs/mainline.git
>> > git.kde.org:kdelibs/kde-42.git
>> > git.kde.org:kdelibs/kde-41.git
>>
>> does this imply that no histori
On Monday 19 January 2009 10:45:14 Ian Monroe wrote:
> I'm not feeling so bad about the authenticity issue since thiago says
> that we could have a log of who is pushing what on the server side.
> Someone needs to talk to the sysadmins and ask how we could set up
> such a server.
it still requires
On Monday 19 January 2009 03:29:38 Johannes Sixt wrote:
> Has your change been reviewed? No. You just modified Amarok without
> consulting the ones who know it in and out. I'm aware that you know a lot
> about the codebase, and you are a core person as core can be, but
> by-passing the maintainers
On Mon, Jan 19, 2009 at 12:59 PM, Robert Wohlrab wrote:
> On Monday 19 January 2009 19:44:33 Oswald Buddenhagen wrote:
>> On Sun, Jan 18, 2009 at 06:45:47PM +0100, Thiago Macieira wrote:
>> > git.kde.org:kdelibs/mainline.git
>> > git.kde.org:kdelibs/kde-42.git
>> > git.kde.org:kdelibs/kde-41.git
>
On Monday 19 January 2009 19:44:33 Oswald Buddenhagen wrote:
> On Sun, Jan 18, 2009 at 06:45:47PM +0100, Thiago Macieira wrote:
> > git.kde.org:kdelibs/mainline.git
> > git.kde.org:kdelibs/kde-42.git
> > git.kde.org:kdelibs/kde-41.git
>
> does this imply that no historic branches are imported?
Or m
On Sun, Jan 18, 2009 at 06:45:47PM +0100, Thiago Macieira wrote:
> git.kde.org:kdelibs/mainline.git
> git.kde.org:kdelibs/kde-42.git
> git.kde.org:kdelibs/kde-41.git
>
does this imply that no historic branches are imported?
___
Kde-scm-interest mailing li
On Mon, Jan 19, 2009 at 9:07 AM, wrote:
> So how can we move this project forward? Jeff volunteered to help set
> this up, and I'm available too. Have BKO and commit filter hooks been
> written yet?
>
> Casey
>
Well scripty is located in kde-common, the bash script 'makemessages'.
More of scrip
So how can we move this project forward? Jeff volunteered to help set
this up, and I'm available too. Have BKO and commit filter hooks been
written yet?
Casey
___
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listin
On Mon, Jan 19, 2009 at 1:50 AM, Johannes Sixt wrote:
> Ian Monroe schrieb:
>> On Sat, Jan 17, 2009 at 5:17 PM, Thiago Macieira wrote:
>>> * should we use a patch-submission-and-review system? (probably not)
>>
>> no.
>
> Don't throw patch submission and review into the same bucket. I can
> unde
Em Segunda-feira 19 Janeiro 2009, às 13:09:02, Johannes Sixt escreveu:
> Thiago Macieira schrieb:
> > Like I said, it's a social problem.
> >
> > That's the way we've worked for 12 years and we see no reason to change
> > just because we're changing SCM.
> >
> > Now, if we decide that it is a good
Thiago Macieira schrieb:
> Like I said, it's a social problem.
>
> That's the way we've worked for 12 years and we see no reason to change just
> because we're changing SCM.
>
> Now, if we decide that it is a good thing to do, it might be a good
> opportunity to do it while we change SCMs. But
Em Segunda-feira 19 Janeiro 2009, às 09:29:38, Johannes Sixt escreveu:
> Has your change been reviewed? No. You just modified Amarok without
> consulting the ones who know it in and out. I'm aware that you know a lot
> about the codebase, and you are a core person as core can be, but
> by-passing t
Thiago Macieira schrieb:
> Johannes Sixt wrote:
>> Thiago Macieira schrieb:
>>> Ian Monroe wrote:
> * the unresolved issue of accountability
This is the main issue I see. I hear there are solutions though?
>>> We have to see whether Git notes solves the problem.
>> I still don't see a nee
15 matches
Mail list logo
