From: Jeff King <peff@peff.net>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] Change "refs/" references to symbolic constants
Date: Tue, 2 Oct 2007 11:58:01 -0400 [thread overview]
Message-ID: <20071002155800.GA6828@coredump.intra.peff.net> (raw)
In-Reply-To: <200710020941.05288.andyparkins@gmail.com>
On Tue, Oct 02, 2007 at 09:41:03AM +0100, Andy Parkins wrote:
> Excellent! Well done. I spent a couple of hours last night going through
> every changed line and have spotted the TAGS mistake but didn't spot the
> STRLEN being wrong. Amazing how easy it is to become blind to these things.
> There were a couple of errors in "/" placement too, but I don't think they
> were causing any trouble, just doubled up "/" characters.
I wonder if you could check the patch mechanically (i.e., write a script
to confirm that '5' got replaced by tokens equal to '5'), though that
might require some tricky parsing of C.
If you a post an updated version, I will try to read through it
carefully, as two eyes are better than one (er, four eyes, I guess).
> I noticed a couple of places where memcmp() has been used where prefixcmp()
> would work fine. I'm tempted to change them too - what do you think?
> Perhaps a separate patch?
When in doubt, I would suggest a separate patch, as it makes the review
easier.
> I'm happy to do prepare a patch against any revision, I was really
> waiting for feedback from Junio as to how he'd like to manage it.
> Last time I submitted this patch he (quite correctly) asked that I
> delay until after the next point release; of course I promptly found
> other things to do and never resubmitted :-)
Yes, you should definitely listen to Junio on such issues, and not me.
:)
-Peff
next prev parent reply other threads:[~2007-10-02 15:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 12:59 [PATCH 1/2] Change "refs/" references to symbolic constants Andy Parkins
2007-10-01 20:41 ` Andy Parkins
2007-10-02 1:16 ` Jeff King
2007-10-02 8:41 ` Andy Parkins
2007-10-02 15:58 ` Jeff King [this message]
2007-10-02 18:16 ` [PATCH] " Andy Parkins
2007-10-02 19:11 ` Jeff King
2007-10-02 19:47 ` Junio C Hamano
2007-10-02 20:48 ` Jeff King
2007-10-03 0:22 ` Junio C Hamano
2007-10-03 2:58 ` Jeff King
2007-10-03 4:05 ` Johannes Schindelin
2007-10-03 4:30 ` Jeff King
2007-10-03 11:30 ` Andreas Ericsson
2007-10-03 7:37 ` Andy Parkins
2007-10-03 7:50 ` Andy Parkins
2007-10-03 11:13 ` Andy Parkins
2007-10-02 17:59 ` [PATCH 1/2] " Junio C Hamano
2007-10-03 7:40 ` Andy Parkins
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=20071002155800.GA6828@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=andyparkins@gmail.com \
--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 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).