[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:39:09 -0600 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc12 Lightning/1.0b1 Thunderbird/3.0.4 |
On 04/22/2010 11:28 AM, Glenn Morris wrote:
> Sorry, I know nothing about "git send-email". Things should work fine
> if you just hit followup/reply-to-all in a normal mail client.
'git send-email' is a means of using git to generate and send the email
independently of any email client; it cuts out the steps of creating the
patch file and attaching it to an email. It includes the option
--in-reply-to. In the case of the email in question, I used it with the
result that the email included both In-Reply-To: and References: of
<address@hidden>, which matches the original poster's
message id.
>
> You can reply to either bug-coreutils or address@hidden and it should
> work fine. Using the latter makes life easier. If you reply to
> bug-coreutils, in order to work out the bug number we need either "Re:
> bug####" in the subject, or a "Re:" prefix at the start of the subject
> and a References: or In-Reply-To: header pointing to the original
> report (this is a somewhat experimental feature).
Then what I did with git should have worked.
--
Eric Blake address@hidden +1-801-349-2682
Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature