From: Tay Ray Chuan <rctay89@gmail.com>
To: jackylee <jacky.liye@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] refactor commit_graft_pos using general sha1_pos function
Date: Fri, 26 Feb 2010 11:04:25 +0800 [thread overview]
Message-ID: <be6fef0d1002251904q59e12149lc3010b3587b00f8c@mail.gmail.com> (raw)
In-Reply-To: <4B87EBD2.3060007@gmail.com>
Hi,
On Fri, Feb 26, 2010 at 11:42 PM, jackylee <jacky.liye@gmail.com> wrote:
> code cleanup according to git janitor page, replace sha1 lookup function with "sha1_pos" general binary search function
>
> Signed-off-by: jacky.liye <jacky.liye@gmail.com>
please sign off with your real name. See
http://repo.or.cz/w/git.git?a=blob;f=Documentation/SubmittingPatches;hb=HEAD
for the importance of the sign-off.
--
Cheers,
Ray Chuan
next prev parent reply other threads:[~2010-02-26 3:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 15:42 [PATCH] refactor commit_graft_pos using general sha1_pos function jackylee
2010-02-26 3:04 ` Tay Ray Chuan [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-26 16:31 jackylee
2010-02-25 19:57 jacky.liye
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=be6fef0d1002251904q59e12149lc3010b3587b00f8c@mail.gmail.com \
--to=rctay89@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jacky.liye@gmail.com \
/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).