: nothing against you Wolfgang, you just happened the one pushing
these changes ;)
-- Forwarded message --
From: Wolfgang Borgert deba...@moszumanska.debian.org
Date: Tue, Sep 23, 2014 at 10:19 PM
Subject: [Python-modules-commits] [python-mplexporter] 135/135: Merge
pull
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
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 some kind
On October 9, 2014 5:36:02 AM EDT, Raphael Hertzog hert...@debian.org 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
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
more
On October 9, 2014 10:43:38 AM EDT, Barry Warsaw ba...@debian.org 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
On 9 October 2014 20:57, Scott Kitterman deb...@kitterman.com wrote:
On October 9, 2014 10:43:38 AM EDT, Barry Warsaw ba...@debian.org 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
On Friday, October 10, 2014 00:22:42 Dimitri John Ledkov wrote:
On 9 October 2014 20:57, Scott Kitterman deb...@kitterman.com wrote:
On October 9, 2014 10:43:38 AM EDT, Barry Warsaw ba...@debian.org wrote:
On Oct 09, 2014, at 10:19 AM, Scott Kitterman wrote:
Upstream commits are off topic.
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 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 all share
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,
would really
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 is the one
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, it's
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
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 commits will
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, and
On Wed, Sep 24, 2014 at 8:14 AM, Julian Taylor
jtaylor.deb...@googlemail.com 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
PM
Subject: [Python-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
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 side
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 September 23, 2014 6:46:58 PM EDT, Charles Plessy ple...@debian.org 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
21 matches
Mail list logo
