From: David Kastrup <dak@gnu.org>
To: git@vger.kernel.org
Subject: Re: [PATCH] builtin/blame.c::find_copy_in_blob: no need to scan for line end
Date: Sat, 22 Feb 2014 16:52:52 +0100 [thread overview]
Message-ID: <874n3rf8kr.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <1393084157-23137-1-git-send-email-dak@gnu.org> (David Kastrup's message of "Sat, 22 Feb 2014 16:49:17 +0100")
David Kastrup <dak@gnu.org> writes:
Oh, good grief. Forgot to sign off, and on rereading, the commit
message is clearly subfabulous. So forget this one. The content is
fine, though.
--
David Kastrup
prev parent reply other threads:[~2014-02-22 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-22 15:49 [PATCH] builtin/blame.c::find_copy_in_blob: no need to scan for line end David Kastrup
2014-02-22 15:52 ` David Kastrup [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=874n3rf8kr.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=git@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.