Package: git-core
Version: 1:1.5.3.8-1
Severity: wishlist
Hello,
if the project description is quite long, the email subject becomes
really long. I'd like an option to have the project name instead of the
project description in the email subject. To avoid regressions, the
project name should default to the project description.
BTW, as soon as the BTS will assign a bug number, I'll post the git
patch.
Thx, bye,
Gismo / Luca
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages git-core depends on:
ii cpio 2.9-9 GNU cpio -- a program to manage ar
ii libc6 2.7-6 GNU C Library: Shared libraries
ii libcurl3-gnutls 7.17.1-1+b1 Multi-protocol file transfer libra
ii libdigest-sha1-perl 2.11-2 NIST SHA-1 message digest algorith
ii liberror-perl 0.17-1 Perl module for error/exception ha
ii libexpat1 1.95.8-4 XML parsing C library - runtime li
ii perl-modules 5.8.8-12 Core Perl modules
ii zlib1g 1:1.2.3.3.dfsg-11 compression library - runtime
Versions of packages git-core recommends:
ii curl 7.17.1-1+b1 Get a file from an HTTP, HTTPS or
ii less 418-1 Pager program similar to more
ii openssh-client [ssh-client] 1:4.7p1-2 secure shell client, an rlogin/rsh
ii patch 2.5.9-4 Apply a diff file to an original
ii rsync 2.6.9-6 fast remote file copy program (lik
-- no debconf information
tags 463336 + patch
thanks
Hello!
On Thu, 31 Jan 2008 00:19:04 +0100, Luca Capello wrote:
> BTW, as soon as the BTS will assign a bug number, I'll post the git
> patch.
Attached and also available on my git repository [1].
Thx, bye,
Gismo / Luca
Footnotes:
[1] http://git.debian.org/?p=users/gismo/git.git;a=summary
Hi Luca,
On Thu, Jan 31, 2008 at 12:19:04AM +0100, Luca Capello wrote:
> BTW, as soon as the BTS will assign a bug number, I'll post the git
> patch.
Just a side-note: Are you aware that you may send a patch (including the
appropriate tag) along with your original bug report?
Cheers,
Sebastian
--
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/
Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin
Hi Luca,
On Fri, Feb 01, 2008 at 03:50:17PM +0100, Luca Capello wrote:
> On Fri, 01 Feb 2008 14:38:37 +0100, Sebastian Harl wrote:
> > On Thu, Jan 31, 2008 at 12:19:04AM +0100, Luca Capello wrote:
> >> BTW, as soon as the BTS will assign a bug number, I'll post the git
> >> patch.
> >
> > Just a side-note: Are you aware that you may send a patch (including
> > the appropriate tag) along with your original bug report?
>
> For the patch: do you mean the one at [1], also available on my git
> repository [2]? In case not, what kind of patch?
[...]
No, I was just saying that you do not need to wait for a bug number
being assigned to a bug if you want to provide a patch - you can simply
include that patch into your original bug report (i.e. the E-mail you're
sending to [email protected]). This was just meant as a general note and not
related to any specific bug report.
Cheers,
Sebastian
PS: I should not have replied to the BTS in the first place - please
take this to a private conversation if you have further comments.
--
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/
Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin
Hi Sebastian!
On Fri, 01 Feb 2008 16:41:18 +0100, Sebastian Harl wrote:
> PS: I should not have replied to the BTS in the first place - please
> take this to a private conversation if you have further comments.
Keeping into the PTS, since I think it's a useful discussion.
> On Fri, Feb 01, 2008 at 03:50:17PM +0100, Luca Capello wrote:
>> On Fri, 01 Feb 2008 14:38:37 +0100, Sebastian Harl wrote:
>> > On Thu, Jan 31, 2008 at 12:19:04AM +0100, Luca Capello wrote:
>> >> BTW, as soon as the BTS will assign a bug number, I'll post the git
>> >> patch.
>> >
>> > Just a side-note: Are you aware that you may send a patch (including
>> > the appropriate tag) along with your original bug report?
>>
>> For the patch: do you mean the one at [1], also available on my git
>> repository [2]? In case not, what kind of patch?
> [...]
>
> No, I was just saying that you do not need to wait for a bug number
> being assigned to a bug if you want to provide a patch
I based my patch to the one fixing #428418 [1] (upstream at [2]): the
idea is that the *git* patch should be "complete", thus also including
the Debian bug number the patch is trying to fix.
Hope that now it's clear, since this is my workflow every time I deal
with Debian bugs against upstream.
Thx, bye,
Gismo / Luca
Footnotes:
[1] http://bugs.debian.org/428418
[2] http://git.kernel.org/?p=git/git.git;a=commit;h=e7509ee388480046a685f885431291f484de66de
Hi Luca,
On Sat, Feb 02, 2008 at 11:44:04AM +0100, Luca Capello wrote:
> On Fri, 01 Feb 2008 16:41:18 +0100, Sebastian Harl wrote:
> > On Fri, Feb 01, 2008 at 03:50:17PM +0100, Luca Capello wrote:
> >> On Fri, 01 Feb 2008 14:38:37 +0100, Sebastian Harl wrote:
> >> > On Thu, Jan 31, 2008 at 12:19:04AM +0100, Luca Capello wrote:
> >> >> BTW, as soon as the BTS will assign a bug number, I'll post the git
> >> >> patch.
> >> >
> >> > Just a side-note: Are you aware that you may send a patch (including
> >> > the appropriate tag) along with your original bug report?
> >>
> >> For the patch: do you mean the one at [1], also available on my git
> >> repository [2]? In case not, what kind of patch?
> > [...]
> >
> > No, I was just saying that you do not need to wait for a bug number
> > being assigned to a bug if you want to provide a patch
>
> I based my patch to the one fixing #428418 [1] (upstream at [2]): the
> idea is that the *git* patch should be "complete", thus also including
> the Debian bug number the patch is trying to fix.
Oh, I see - sorry for the noise then :-)
Cheers,
Sebastian
--
Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/
Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin
Subject: Re: Bug#463336: git-core: [hooks/post-receive-email] option to set
the project name
Date: Fri, 8 Feb 2008 14:01:42 +0000
On Fri, Feb 01, 2008 at 03:50:17PM +0100, Luca Capello wrote:
> Otherwise, maybe are you talking about sending the patch upstream? I'd
> avoid that, since AFAIK git-core maintainer (hi, Gerrit!) has commit
> access to the upstream git [3] and thus I'd prefer him dealing with
> upstream.
Hi Luca, I don't have direct commit access, but submit my patches to the
git mailing list where Junio picks them up or not, or comments them.
So if you like you can do just the same instead of waiting for me until
I get to them. I skimmed over the changes, and am currently not sure
whether they would be accepted as is. If not, the list members usually
give good advise in their followups.
Regards, Gerrit.
Acknowledgement sent
to Jonathan Nieder <[email protected]>:
Extra info received and forwarded to list. Copy sent to Gerrit Pape <[email protected]>.
(Sat, 15 May 2010 20:45:06 GMT) (full text, mbox, link).
Subject: Re: [hooks/post-receive-email] option to set the project name
Date: Sat, 15 May 2010 15:40:39 -0500
reassign 463336 git git/1:1.5.3.8-1
found 463336 git/1:1.7.1-1
tags 463336 + upstream
quit
Hi Luca,
Luca Capello wrote:
> if the project description is quite long, the email subject becomes
> really long. I'd like an option to have the project name instead of the
> project description in the email subject. To avoid regressions, the
> project name should default to the project description.
Same comments as in http://bugs.debian.org/463316 apply here: what do you
think of Mike Frysinger’s more general solution?
Personally, I suspect this points to it being useful to add more
user-defined substitutions to the hooks.emailsubject variable. I am not
so happy with complicating the configuration more by default.
Thanks for the report and patch[1],
Jonathan
[1] http://git.debian.org/?p=users/gismo/git.git;h=57c345f2
Changed Bug title to 'git/post-receive-email: allow customizing the subject, intro, and footer' from 'git-core: [hooks/post-receive-email] option to set the project name'
Request was from Jonathan Nieder <[email protected]>
to [email protected].
(Sat, 19 Feb 2011 02:51:04 GMT) (full text, mbox, link).
Subject: Re: git-core: [hooks/post-receive-email] option to set the project
name
Date: Fri, 18 Feb 2011 20:45:58 -0600
tags 463316 + patch
merge 463336 463316
retitle 463316 git/post-receive-email: allow customizing the subject, intro, and footer
# [1]
forwarded 463316 http://thread.gmane.org/gmane.comp.version-control.git/137426
quit
Hi!
Luca Capello wrote:
> if the project description is quite long, the email subject becomes
> really long.
Since I never use post-receive-email myself, I don't think I'll get
around to this. But I encourage anyone interested to take Mike
Frysinger's patch[1] and build on it or resend it upstream.
Thanks for your work,
Jonathan
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.