[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: extragear/multimedia/amarok/src/configdialog/dialogs
From:       Leo Franchi <lfranchi () kde ! org>
Date:       2009-02-22 22:38:04
Message-ID: C2506385-0C0E-4E2C-87B1-317C6EA9AF86 () kde ! org
[Download RAW message or body]

On 22 Feb 2009, at 22:32, Seb Ruiz wrote:

> 2009/2/23 Lydia Pintscher <lydia@kde.org>:
>> On Sun, Feb 22, 2009 at 23:13, Seb Ruiz <ruiz@kde.org> wrote:
>>> Haha, I've got a bad track record for doing this. First to Hydrogen,
>>> and now to you.
>>>
>>> Well as I always say - the early bird gets the worm, the late one  
>>> gets
>>> to do the conflict merging.
>>
>> Please poke people next time. This is not really cool.
>> With everyone having stuff in their git trees communication about  
>> this
>> becomes 10000 times more important.
>
> No, sorry, I can't. I don't have enough time nowadays to know days in
> advance what I'm going to be hacking on. When I get a few hours free,
> I hack. I'd say that if you're building up giant changesets which are
> likely to conflict, it's the authors responsibility to send out a
> memo.


I agree with seb here. It's impossible to tell people of your planned  
changes, or track down the responsible people and notify them---much  
easier to send a quick email to the list if you have a large patch  
sitting around while you work on it, i think.

leo

---
Leo Franchi				(650) 704 3680
Tufts University 2010

lfranchi@kde.org
leonardo.franchi@tufts.edu

[prev in list] [next in list] [prev in thread] [next in thread]