From: Glenn Morris <rgm@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 25969@debbugs.gnu.org
Subject: bug#25969: guix-patches debbugs appears to mangle patches
Date: Mon, 06 Mar 2017 12:46:31 -0500 [thread overview]
Message-ID: <nashmqz4aw.fsf__40051.4374058277$1488822467$gmane$org@fencepost.gnu.org> (raw)
In-Reply-To: <87a88yww0m.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 06 Mar 2017 11:16:09 +0100")
Ludovic Courtès wrote:
> Hello!
>
> Leo Famulari <leo@famulari.name> skribis:
>
>> The guix-patches debbugs thing causes a regression in this workflow by
>> rewriting the commit messages to include the debbugs ticket number.
>>
>> So, a commit that begins with this:
>>
>> gnu: gitolite: Fix shebangs in hooks.
>>
>> ... becomes this:
>>
>> bug#25966: [PATCH 2/2] gnu: gitolite: Fix shebangs in hooks.
>>
>> Am I missing something, or is debbugs really rewriting the patches?
>
> Good question. Maybe Glenn and others at help-debbugs have an idea?
I think it's over the top to describe this as "mangling" or "rewriting"
patches. The system relies on adding a bug number to the subject, so
that replies to the maintainer address can be associated with the right
bug. I don't see any prospect of this changing. If you are using a tool
that is sensitive to the subject line in emails, I can only suggest
using eg a trivial sed command to take out the bug number before passing
the mail to your tool.
next prev parent reply other threads:[~2017-03-06 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-04 22:54 bug#25969: guix-patches debbugs appears to mangle patches Leo Famulari
2017-03-05 12:34 ` ng0
2017-03-05 12:37 ` ng0
2017-03-06 10:16 ` Ludovic Courtès
[not found] ` <87a88yww0m.fsf@gnu.org>
2017-03-06 17:46 ` Glenn Morris [this message]
[not found] ` <nashmqz4aw.fsf@fencepost.gnu.org>
2017-03-06 17:54 ` Eric Blake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='nashmqz4aw.fsf__40051.4374058277$1488822467$gmane$org@fencepost.gnu.org' \
--to=rgm@gnu.org \
--cc=25969@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).