On 2014-10-10 13:13, Matthias Urlichs wrote:
> Looking at that code, IMHO it should be sufficient to add the arguments
> '--' and 'debian' to all calls of "git revlist".
Who can add this?
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble
Hi,
On Fri, 10 Oct 2014, Charles Plessy wrote:
> Le Fri, Oct 10, 2014 at 11:11:46AM +0200, W. Martin Borgert a écrit :
> >
> > Where is the repository of the scripts involved? Maybe I have
> > some spare time this weekend... I hope, it's all sh or Python.
> > I forgot all my Perl.
>
> Hi Martin,
On Friday, October 10, 2014 09:04:32 Barry Warsaw wrote:
> On Oct 10, 2014, at 12:16 AM, Tianon Gravi wrote:
> >At the BoF during DebConf, me and paultag discussed how we use exactly
> >this workflow for Docker stuff in Git, and we love it. We don't ever
> >worry about any kind of upstream commits
On Oct 10, 2014, at 12:16 AM, Tianon Gravi wrote:
>At the BoF during DebConf, me and paultag discussed how we use exactly
>this workflow for Docker stuff in Git, and we love it. We don't ever
>worry about any kind of upstream commits in the packaging, and only
>deal with upstream tarballs/source
Hi,
Charles Plessy:
> https://github.com/mhagger/git-multimail/
>
Looking at that code, IMHO it should be sufficient to add the arguments
'--' and 'debian' to all calls of "git revlist".
--
-- Matthias Urlichs
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subj
Le Fri, Oct 10, 2014 at 11:11:46AM +0200, W. Martin Borgert a écrit :
>
> Where is the repository of the scripts involved? Maybe I have
> some spare time this weekend... I hope, it's all sh or Python.
> I forgot all my Perl.
Hi Martin,
good news, it is in Python :)
https://github.com/mhagge
On 2014-10-10 10:13, Raphael Hertzog wrote:
> On Fri, 10 Oct 2014, W. Martin Borgert wrote:
> > I assume, that the script uses post-receive, so it has access to
> > all commits, including all affected paths. If so, generating only
> > emails or IRC messages when debian/ is involved should be easy.
On Fri, 10 Oct 2014, W. Martin Borgert wrote:
> On 2014-10-10 15:59, Ben Finney wrote:
> > Agreed. This is a direct result of rebasing Debian packaging history
> > onto upstream VCS history, and keeping them all in the same repo as one
> > undifferentiated history, no?
>
> Not sure, but isn't this
On 2014-10-10 15:59, Ben Finney wrote:
> Agreed. This is a direct result of rebasing Debian packaging history
> onto upstream VCS history, and keeping them all in the same repo as one
> undifferentiated history, no?
Not sure, but isn't this more a result of the scripts in use, to
not differentiate
On 9 October 2014 22:59, Ben Finney wrote:
> It's a good illustration of why I much prefer the workflow of a separate
> VCS for the ‘debian/’ directory, merged with upstream source only at
> build time. The results of the merge are in a separate location and are
> never checked into VCS, they're u
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
Scott Kitterman writes:
> 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.
Agreed. This is a direct result of rebasing Debian packaging history
onto upstream V
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
> I wonder, whether some kind of digest function would be possible
> and useful?
how's getting 1 email with 100 upstream commits different to getting
100 emails with upstream commits? (other than it's easier to read these
100 emails and a bit easier to delete digest one)
--
Piotr Ożarowski
(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,
24 matches
Mail list logo
