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
Le Fri, Oct 10, 2014 at 12:03:38AM -0400, Scott Kitterman a écrit :
>
> Changing the number of commits is solving the wrong problem. The problem
> that
> needs to be solved is including upstream commits. That's thoroughly
> uninteresting for a packaging team. Also, it's not just the mails, i
On Friday, October 10, 2014 12:56:41 Charles Plessy wrote:
> Le Thu, Oct 09, 2014 at 11:41:47PM -0400, Scott Kitterman a écrit :
> > On Friday, October 10, 2014 11:08:53 Chow Loong Jin wrote:
> > > On Thu, Oct 09, 2014 at 07:57:48PM -0400, Scott Kitterman wrote:
> > > > [..]
> > > > Presumably "one
Le Thu, Oct 09, 2014 at 11:41:47PM -0400, Scott Kitterman a écrit :
> On Friday, October 10, 2014 11:08:53 Chow Loong Jin wrote:
> > On Thu, Oct 09, 2014 at 07:57:48PM -0400, Scott Kitterman wrote:
> > > [..]
> > > Presumably "one" is the one who set up the git repos. I, for another one,
> > > wou
On Friday, October 10, 2014 11:08:53 Chow Loong Jin wrote:
> On Thu, Oct 09, 2014 at 07:57:48PM -0400, Scott Kitterman wrote:
> > [..]
> > Presumably "one" is the one who set up the git repos. I, for another one,
> > would really appreciate it if someone would take care of this.
>
> Don't they al
On Thu, Oct 09, 2014 at 07:57:48PM -0400, Scott Kitterman wrote:
> [..]
> Presumably "one" is the one who set up the git repos. I, for another one,
> would really appreciate it if someone would take care of this.
Don't they all share the hook script?
--
Kind regards,
Loong Jin
signature.asc
On Friday, October 10, 2014 00:22:42 Dimitri John Ledkov wrote:
> On 9 October 2014 20:57, Scott Kitterman wrote:
> > On October 9, 2014 10:43:38 AM EDT, Barry Warsaw wrote:
> >>On Oct 09, 2014, at 10:19 AM, Scott Kitterman wrote:
> >>>Upstream commits are off topic.
> >>
> >>Agreed. There's no
On 9 October 2014 20:57, Scott Kitterman wrote:
> On October 9, 2014 10:43:38 AM EDT, Barry Warsaw wrote:
>>On Oct 09, 2014, at 10:19 AM, Scott Kitterman wrote:
>>
>>>Upstream commits are off topic.
>>
>>Agreed. There's no reason why we need notifications of upstream
>>commits,
>>though I don't
On October 9, 2014 10:43:38 AM EDT, Barry Warsaw wrote:
>On Oct 09, 2014, at 10:19 AM, Scott Kitterman wrote:
>
>>Upstream commits are off topic.
>
>Agreed. There's no reason why we need notifications of upstream
>commits,
>though I don't know if it's possible to filter them out.
>
>>I'm probably
On Oct 09, 2014, at 10:19 AM, Scott Kitterman wrote:
>Upstream commits are off topic.
Agreed. There's no reason why we need notifications of upstream commits,
though I don't know if it's possible to filter them out.
>I'm probably going to give up on hanging out on #debian-python once we get
>mo
On October 9, 2014 5:36:02 AM EDT, Raphael Hertzog wrote:
>On Thu, 09 Oct 2014, W. Martin Borgert wrote:
>> On 2014-10-09 10:02, Raphael Hertzog wrote:
>> > I fixed the default configuration in setup-repository to limit to
>20
>> > commits per push as a maximum. And I also limited the size of
>ind
On Thu, 09 Oct 2014, W. Martin Borgert wrote:
> On 2014-10-09 10:02, Raphael Hertzog wrote:
> > I fixed the default configuration in setup-repository to limit to 20
> > commits per push as a maximum. And I also limited the size of individual
> > commit emails to 1000 lines.
>
> I wonder, whether s
(Please, when using email, choose an appropriate subject. Thanks!)
On 2014-10-09 10:02, Raphael Hertzog wrote:
> I fixed the default configuration in setup-repository to limit to 20
> commits per push as a maximum. And I also limited the size of individual
> commit emails to 1000 lines.
I wonder,
On Thu, 09 Oct 2014, Sandro Tosi wrote:
> so is there any chance you stop this commit storm madness anytime
> soon? another bunch of >300 commit messages arrive this night
I fixed the default configuration in setup-repository to limit to 20
commits per push as a maximum. And I also limited the
ratio on the ml?
>
> Sandro
>
> PS: nothing against you Wolfgang, you just happened the one pushing
> these changes ;)
>
>
> -- Forwarded message --
> From: Wolfgang Borgert
> Date: Tue, Sep 23, 2014 at 10:19 PM
> Subject: [Python-modules-commits] [pyt
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
on-modules-commits] [python-mplexporter] 135/135: Merge
pull request #30 from rainwoodman/patch-1
To: python-modules-comm...@lists.alioth.debian.org,
python-mplexporter_...@packages.qa.debian.org
This is an automated email from the git hooks/post-receive script.
debacle pushed a commit to branch
23 matches
Mail list logo
