From: Junio C Hamano <junkio@cox.net>
To: "Santi Béjar" <sbejar@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Use "hash1..hash2" instead of "from hash1 to hash2"
Date: Thu, 28 Sep 2006 19:28:59 -0700 [thread overview]
Message-ID: <7v7iznquc4.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 877iznbq0v.fsf@gmail.com
This kind of "appearance only" change needs better
justification. Not that I am saying "from .. to" is better for
such and such reasons, but that's how it's been, so if you are
proposing to change it, you need to defend why it would help
users (otherwise I would get hate mails that say "why did you
merge it -- it broke my work habit in such and such way").
You may be doing this for brevity. In that case, it could
also be worth shortening them to n unique digits; do we have a
command to get "here is the SHA-1; give me its unique
abbreviation at least n letters long but make it longer as
needed to keep it unique"?
You may be doing this to help Cut & Paste. Using A..B without
spaces in between makes it easy to grab both at the same time as
a range to give them to "git log". At the same time it makes it
harder to pick only A or B, so this is two-edged.
next prev parent reply other threads:[~2006-09-29 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 22:11 [PATCH] Use "hash1..hash2" instead of "from hash1 to hash2" Santi Béjar
2006-09-29 2:28 ` Junio C Hamano [this message]
2006-09-29 19:53 ` Carl Worth
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=7v7iznquc4.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=sbejar@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).