From: Alan Mackenzie <acm@muc.de>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Juanma Barranquero <lekktu@gmail.com>,
Emacs developers <emacs-devel@gnu.org>,
Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: [Emacs-diffs] trunk r116644: ChangeLog entries should be usable without the VCS
Date: Mon, 3 Mar 2014 22:35:35 +0000 [thread overview]
Message-ID: <20140303223535.GE3841@acm.acm> (raw)
In-Reply-To: <87fvmyvrw7.fsf@igel.home>
'Evening, Andreas!
On Mon, Mar 03, 2014 at 11:28:24PM +0100, Andreas Schwab wrote:
> Alan Mackenzie <acm@muc.de> writes:
> > Hi, Andreas.
> > On Mon, Mar 03, 2014 at 10:23:22PM +0100, Andreas Schwab wrote:
> >> Dmitry Gutov <dgutov@yandex.ru> writes:
> >> > Being able to refer to commits directly is very useful, and especially
> >> > in Git where revision identifiers (hashes) are global.
> >> Using only the hash is frowned upon, the best practice is to follow it
> >> with the subject of the commit message.
> > Is this because the hashes don't count as human-readable, in contrast to
> > the sequential revision numbers that other systems (such as bzr and hg)
> > use?
> Neither revision numbers nor hashes are readable.
On the contrary, r116644 is eminently readable and memorisable, so much
so that I was able to transfer it to a "bzr log -r116644" instruction
without even having to bother with copy and paste.
Earlier on in the evening, I'd just done an informal bisect on the CC
Mode repository using "hg cat -r768", etc. Worked like a dream.
Things are a bit different if you've got to use some arbitrary head of
something like df91e9880a3156ae1d236e88f.....
> Andreas.
> --
> Andreas Schwab, schwab@linux-m68k.org
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2014-03-03 22:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1WKWHG-000385-BB@vcs.savannah.gnu.org>
2014-03-03 17:09 ` [Emacs-diffs] trunk r116644: ChangeLog entries should be usable without the VCS Juanma Barranquero
2014-03-03 17:31 ` David Kastrup
2014-03-03 18:06 ` Juanma Barranquero
2014-03-03 18:09 ` Alan Mackenzie
2014-03-03 18:19 ` Juanma Barranquero
2014-03-03 19:22 ` Dmitry Gutov
2014-03-03 21:23 ` Andreas Schwab
2014-03-03 22:00 ` Alan Mackenzie
2014-03-03 22:28 ` Andreas Schwab
2014-03-03 22:35 ` Alan Mackenzie [this message]
2014-03-03 22:53 ` Andreas Schwab
2014-03-04 8:26 ` Stephen J. Turnbull
2014-03-04 16:35 ` Eli Zaretskii
2014-03-04 0:01 ` Dmitry Gutov
2014-03-04 17:28 ` Glenn Morris
2014-03-04 18:05 ` Juanma Barranquero
2014-03-04 18:13 ` David Kastrup
2014-03-04 18:19 ` Juanma Barranquero
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140303223535.GE3841@acm.acm \
--to=acm@muc.de \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).