From: Kyle McMartin <kyle@mcmartin.ca>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git format-patch shell quoting bug
Date: Sat, 7 Jan 2006 14:16:40 -0500 [thread overview]
Message-ID: <20060107191640.GD15084@quicksilver.road.mcmartin.ca> (raw)
In-Reply-To: <7vhd8gpxt3.fsf@assigned-by-dhcp.cox.net>
On Fri, Jan 06, 2006 at 06:38:16PM -0800, Junio C Hamano wrote:
> commit aa66c7ec77d474b737da607d6cb2d07f56628def
> Author: Junio C Hamano <junkio@cox.net>
> Date: Thu Jan 5 19:50:37 2006 -0800
>
> format-patch/commit: Quote single quote in the author name properly.
>
> Noticed by Kyle McMartin.
>
> Signed-off-by: Junio C Hamano <junkio@cox.net>
>
> The bug was present ever since format-patch started picking up
> the original authorship information from the commits, done on
> July 22nd last year, between v0.99.1 and v0.99.2.
>
Awesome. Thanks very much for fixing this!
Cheers,
Kyle
prev parent reply other threads:[~2006-01-07 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 4:55 git format-patch shell quoting bug Kyle McMartin
2006-01-07 2:38 ` Junio C Hamano
2006-01-07 19:16 ` Kyle McMartin [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060107191640.GD15084@quicksilver.road.mcmartin.ca \
--to=kyle@mcmartin.ca \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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.
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 NNTP newsgroup(s).