On 09/24/2014 10:51 AM, Scott Kitterman wrote:
> In addition to the mail list, the commits for just one package made
> #debian-python unusable a couple of times today.
The KGB bot is configurable to have limits. I did that with my own KGB
bot, and it works every well.
On 09/24/2014 10:51 AM, Scot
On Wed, Sep 24, 2014 at 8:14 AM, Julian Taylor
wrote:
> On 24.09.2014 08:14, Matthias Urlichs wrote:
>> Hi,
>>
>> Scott Kitterman:
>>> This kind of nonsense is a great reason to stay with svn.
>>>
>> Nah. It's a great reason to teach the tool in question to be *way* more
>> reasonable. Who needs a
Hi,
On Wed, 24 Sep 2014, Julian Taylor wrote:
> > Nah. It's a great reason to teach the tool in question to be *way* more
> > reasonable. Who needs a single email per commit? Esp. since the number of
> > actual commits will go way up with increased git usage – feature branches
> > are easy in git,
On 24.09.2014 08:14, Matthias Urlichs wrote:
> Hi,
>
> Scott Kitterman:
>> This kind of nonsense is a great reason to stay with svn.
>>
> Nah. It's a great reason to teach the tool in question to be *way* more
> reasonable. Who needs a single email per commit? Esp. since the number of
> actual com
Hi,
Scott Kitterman:
> This kind of nonsense is a great reason to stay with svn.
>
Nah. It's a great reason to teach the tool in question to be *way* more
reasonable. Who needs a single email per commit? Esp. since the number of
actual commits will go way up with increased git usage – feature bra
On September 23, 2014 6:46:58 PM EDT, Charles Plessy wrote:
>Le Tue, Sep 23, 2014 at 10:29:10PM +0100, Sandro Tosi a écrit :
>> Hi all,
>> there's some people who's subscribed to the commit ml, so getting all
>> the changes done to our repos. Now, with the transition to git we are
>> getting this:
Le Tue, Sep 23, 2014 at 10:29:10PM +0100, Sandro Tosi a écrit :
> Hi all,
> there's some people who's subscribed to the commit ml, so getting all
> the changes done to our repos. Now, with the transition to git we are
> getting this: 135 emails for updating a package (and these are only
> upstream
On 2014-09-23 22:29, Sandro Tosi wrote:
> there's some people who's subscribed to the commit ml, so getting all
> the changes done to our repos. Now, with the transition to git we are
> getting this: 135 emails for updating a package (and these are only
> upstream changes). Did you consider this si
Hi all,
there's some people who's subscribed to the commit ml, so getting all
the changes done to our repos. Now, with the transition to git we are
getting this: 135 emails for updating a package (and these are only
upstream changes). Did you consider this side effect? Do you have a
plan to reduce
9 matches
Mail list logo
