Debian Bug report logs - #463336
git/post-receive-email: allow customizing the subject, intro, and footer

Full log

Message #32 received at [email protected] (full text, mbox, reply):

Received: (at 463336) by bugs.debian.org; 2 Feb 2008 10:50:38 +0000
From [email protected] Sat Feb 02 10:50:38 2008
X-Spam-Checker-Version: SpamAssassin 3.1.4-bugs.debian.org_2005_01_02 
	(2006-07-26) on rietz.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-5.8 required=4.0 tests=BAYES_00,FORGED_RCVD_HELO,
	HAS_BUG_NUMBER,IMPRONONCABLE_2,MURPHY_DRUGS_REL8 autolearn=no 
	version=3.1.4-bugs.debian.org_2005_01_02
Return-path: <[email protected]>
Received: from victor.unige.ch ([129.194.9.224])
	by rietz.debian.org with esmtp (Exim 4.63)
	(envelope-from <[email protected]>)
	id 1JLFxF-0004wX-Rb
	for [email protected]; Sat, 02 Feb 2008 10:50:38 +0000
MIME-version: 1.0
Received: from gismo.pca.it (adsl-ull-98-160.46-151.net24.it [151.46.160.98])
 by victor.unige.ch
 (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit))
 with ESMTPSA id <[email protected]> for [email protected];
 Sat, 02 Feb 2008 11:50:31 +0100 (MET)
Received: by gismo.pca.it (Postfix, from userid 1000)	id EC16D5A0AF; Sat,
 02 Feb 2008 11:44:12 +0100 (CET)
From: Luca Capello <[email protected]>
To: Sebastian Harl <[email protected]>
Cc: [email protected]
Subject: Re: Bug#463336: git-core: [hooks/post-receive-email] option to set the
 project name
References: <[email protected]>
 <[email protected]> <[email protected]>
 <[email protected]>
Date: Sat, 02 Feb 2008 11:44:04 +0100
In-reply-to: <[email protected]>
Message-id: <[email protected]>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.50 (gnu/linux)
Content-type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1;
 protocol="application/pgp-signature"

[Message part 1 (text/plain, inline)]

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

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.