From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: Re: [RFC/PATCH] Change "refs/" references to symbolic constants
Date: Sun, 17 Dec 2006 09:00:18 +0000 [thread overview]
Message-ID: <200612170900.19856.andyparkins@gmail.com> (raw)
In-Reply-To: <7vslffcy80.fsf@assigned-by-dhcp.cox.net>
On Saturday 2006, December 16 21:44, Junio C Hamano wrote:
> This is not rejected nor forgotten but has not been applied yet,
> and may not be immediately.
Oh good.
> I would love to have this; it would reduce mistakes (spelling
> "refs/head/" would silently compile fine and result in a broken
> command, while spelling PATH_REFS_HEAD would be caught by the
> compiler).
I'd not even considered that; I liked it because of a natural disinclination
towards repeated use semanitcally identical literals.
> A sad thing is this needs to be done when things are relatively
> quiescent.
While true - is there ever such a time? :-)
On the other hand, this is (hopefully) a zero-impact change, and should leave
the object the same... I might even test it by comparing objects.
> So I would apply this before v1.5.0 (or a replacement, if you
> have updates), but it might have to wait a bit until I I can say
> "ok, no big patches to C part is pending right now and it is a
> good time to do this clean-up".
If I know it's wanted I will happily maintain it indefinitely. It's part of
my rebase on master set anyway, so it's no pain to do so. I'll keep an eye
out for quiet times, or if you prod me when you want it I'll make you a
rebased version instantly.
While we're on this subject, does the same apply to my hashsize literals patch
which swapped 20 for HASH_WIDTH?
Andy
--
Dr Andrew Parkins, M Eng (Hons), AMIEE
prev parent reply other threads:[~2006-12-17 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 16:44 [RFC/PATCH] Change "refs/" references to symbolic constants Andy Parkins
2006-12-16 21:44 ` Junio C Hamano
2006-12-17 9:00 ` Andy Parkins [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=200612170900.19856.andyparkins@gmail.com \
--to=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).