all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: esr@thyrsus.com
Cc: handa@gnu.org, Eli Zaretskii <eliz@gnu.org>,
	rozzin@geekspace.com, Andreas Schwab <schwab@linux-m68k.org>,
	emacs-devel@gnu.org
Subject: Re: Can anyone correct the Bazaar reference "revno:111954.1.97"?
Date: Mon, 03 Mar 2014 14:35:13 +0900	[thread overview]
Message-ID: <87a9d7sv3i.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <20140303034024.GA8371@thyrsus.com>

Eric S. Raymond writes:

 > I expect the trunk commit is what a person reading that comment
 > would want to refer back to - but, as previously noted, the
 > question gets a bit philosophical.

Sure, but it's also pragmatic.  The Emacs workflow does have a
distinguished mainline.  While Emacs developers often use branches
privately, they communicate with each other about changes by merging
to trunk, rather than by posting a branch URL.  If this merge causes a
problem, the fix is then committed to trunk.  (In projects with a
formalized workflow, this is often referred to as commit-and-review.)

So, pragmatically, trunk is the obvious default point of reference
unless explicitly specified otherwise -- and there're really nothing
else that would serve.  These references are also stable as long as
appropriate push controls are in effect.

I don't see any good reason for you to avoid that convention.




  reply	other threads:[~2014-03-03  5:35 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             ` Policy on referencing/abbreviating git commit-IDs, going forward? (was: Can anyone correct the Bazaar reference "revno:111954.1.97"?) Joshua Judson Rosen
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 [this message]
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=87a9d7sv3i.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=esr@thyrsus.com \
    --cc=handa@gnu.org \
    --cc=rozzin@geekspace.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 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.