From: Joshua Judson Rosen <rozzin@geekspace.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: esr@thyrsus.com, handa@gnu.org, Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org
Subject: Policy on referencing/abbreviating git commit-IDs, going forward? (was: Can anyone correct the Bazaar reference "revno:111954.1.97"?)
Date: Sun, 02 Mar 2014 15:01:50 -0500 [thread overview]
Message-ID: <87r46kv07l.fsf_-_@slice.rozzin.com> (raw)
In-Reply-To: <871tykihi1.fsf@igel.home> (Andreas Schwab's message of "Sun, 02 Mar 2014 19:26:46 +0100")
Andreas Schwab <schwab@linux-m68k.org> writes:
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > This is bzr, not git, so the diffs aren't the whole story.
>
> There is no difference between git and bzr wrt. to the DAG. Only the
> names they use are different.
There is an interesting `bzr vs. git' question here, though--because of
the differences in the way revisions are named: when you run into the
analogous "I can't tell what this reference is to" problem in git, how
will you deal with it? When someone writes a abbreviated git sha1sum
into a changelog / commit message because just the first 7 or
howevermany hexits was enough to unambiguously identify the referenced
commit-object in their development environment at the time when they
were committing their change, and then a later commit/merge makes that
abbreviation ambiguous, how will you trace out the now-ambiguously-
abbreviated commit? e.g.: up through July 29 2012, "7a62fbf"
unambiguously identified a commit from October 24 2007; on July 30 2012,
"7a62fbf" stopped being unambiguous.
--
"'tis an ill wind that blows no minds."
next prev parent reply other threads:[~2014-03-02 20:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 17:13 Can anyone correct the Bazaar reference "revno:111954.1.97"? Eric S. Raymond
2014-03-01 18:24 ` Eli Zaretskii
2014-03-01 18:43 ` Eric S. Raymond
2014-03-01 21:35 ` Joshua Judson Rosen
2014-03-01 22:02 ` Eric S. Raymond
2014-03-02 3:47 ` Joshua Judson Rosen
2014-03-02 17:44 ` Eli Zaretskii
2014-03-02 18:26 ` Andreas Schwab
2014-03-02 20:01 ` Joshua Judson Rosen [this message]
2014-03-02 20:30 ` Policy on referencing/abbreviating git commit-IDs, going forward? Andreas Schwab
2014-03-02 21:18 ` Joshua Judson Rosen
2014-03-02 20:35 ` Can anyone correct the Bazaar reference "revno:111954.1.97"? Eli Zaretskii
2014-03-02 21:08 ` Andreas Schwab
2014-03-02 3:53 ` Eli Zaretskii
2014-03-02 3:55 ` Eli Zaretskii
2014-03-02 5:53 ` Joshua Judson Rosen
2014-03-02 17:42 ` Eli Zaretskii
2014-03-02 18:25 ` Andreas Schwab
2014-03-02 20:33 ` Eli Zaretskii
2014-03-02 21:10 ` Andreas Schwab
2014-03-02 21:27 ` Eli Zaretskii
2014-03-02 22:14 ` Andreas Schwab
2014-03-03 3:35 ` Eli Zaretskii
2014-03-03 3:40 ` Eric S. Raymond
2014-03-03 5:35 ` Stephen J. Turnbull
2014-03-03 5:49 ` Eric S. Raymond
2014-03-02 19:08 ` Joshua Judson Rosen
2014-03-02 20:38 ` Eli Zaretskii
2014-03-02 22:00 ` Joshua Judson Rosen
2014-03-02 22:15 ` Andreas Schwab
2014-03-02 22:22 ` Joshua Judson Rosen
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=87r46kv07l.fsf_-_@slice.rozzin.com \
--to=rozzin@geekspace.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.com \
--cc=handa@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.