[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bug#5996: [PATCH] base64: always treat input in binary mode

From: Eric Blake
Subject: Re: bug#5996: [PATCH] base64: always treat input in binary mode
Date: Thu, 22 Apr 2010 11:11:04 -0600
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20100330 Fedora/3.0.4-1.fc12 Lightning/1.0b1 Thunderbird/3.0.4

[migrating to help-debbugs]

On 04/22/2010 11:00 AM, Glenn Morris wrote:
> Hi,
> The following message got resent to bug-gnu-emacs rather than
> bug-coreutils, because debbugs got confused.
> We can discuss the reasons on help-debbugs if anyone is interested.
> (Short answer: it looks like the mail you sent had two separate To:
> headers, and a changed Subject: header with no bug number, both of
> which confused debbugs. It may be possible to improve this a bit.)

The cause of the dual To: was that I had configured 'git send-email' to
autosend to bug-coreutils, then manually added another --to option to
keep 5996@ in the loop.  Sending to bug-coreutils is good for fresh
patch series, but not so good when trying to send a patch in threaded
reply to an existing bug report, so I have since changed my git
configuration to no longer have an automatic entry.

Unfortunately, since I sent that mail with 'git send-email' and did not
bcc myself, and am not subscribed to bug-gnu-emacs, I didn't see the
actual headers that git ended up using; your email was the first I saw
of what I posted.  I know I changed the subject line as a result of
sending from git, but did I even get the bug number in the subject line,
or is that something that I will have to remember to do manually?

Eric Blake   address@hidden    +1-801-349-2682
Libvirt virtualization library

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]