unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Bazaar references complicate the git transition
Date: Sat, 11 Jan 2014 20:15:24 +0100	[thread overview]
Message-ID: <87zjn2misz.fsf@zigzag.favinet> (raw)
In-Reply-To: <87ha9a2x79.fsf@wanadoo.es> ("Óscar Fuentes"'s message of "Sat, 11 Jan 2014 19:24:42 +0100")

[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]

() Óscar Fuentes <ofv@wanadoo.es>
() Sat, 11 Jan 2014 19:24:42 +0100

   Revision numbers in bug reports and mailing list messages also counts.

   IMHO a file mapping bzr revnos to git SHAs is TRT.

Right.  Operating only on the repo externalizes the "problem", but does
not eliminate it (and in fact sows confusion).  In any case, i think
this is a good opportunity (in the sense of "better sooner than later")
to switch to a VCS-neutral reference scheme for new ChangeLog entries.

I've suggested "DATE, TITLE" before, as that's what i use personally[0],
but i think that won't fly w/ Emacs unless TITLE becomes mandatory.

In hopes of "attacking the problem from above", i tried unsuccessfully
to get TITLE mandatory in the GNU Coding Standards, some years back.
Upon reflection (of the words of the discussion's other participants,
mostly :-D), i've come to accept that such conventions are best decided
at the individual project level, by its maintainers.

So, now i suggest the Emacs maintainers mandate TITLE in the ChangeLog,
and only pending that, the adoption of "DATE, TITLE" as a VCS-neutral
reference.  Otherwise, things can only grow hairier w/ time.


_________________________
[0] E.g., see <http://www.gnuvola.org/software/> and choose any tarball.
    In some of the HACKING files, there is even more related verbiage!


-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2014-01-11 19:15 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11 15:54 Bazaar references complicate the git transition Eric S. Raymond
2014-01-11 16:15 ` Juanma Barranquero
2014-01-11 16:29   ` Eric S. Raymond
2014-01-11 16:53     ` Juanma Barranquero
2014-01-11 16:24 ` David Kastrup
2014-01-11 16:40   ` Eric S. Raymond
2014-01-11 17:23     ` Juanma Barranquero
2014-01-11 22:47     ` Timur Aydin
2014-01-11 23:40       ` Eric S. Raymond
2014-01-11 16:36 ` Eli Zaretskii
2014-01-11 16:43   ` Eric S. Raymond
2014-01-11 17:10 ` David Reitter
2014-01-11 17:27   ` Eric S. Raymond
2014-01-11 17:46     ` David Kastrup
2014-01-11 18:00       ` Andreas Schwab
2014-01-11 18:04     ` Eli Zaretskii
2014-01-11 18:08       ` Eli Zaretskii
2014-01-11 18:24         ` Óscar Fuentes
2014-01-11 19:15           ` Thien-Thi Nguyen [this message]
2014-01-11 19:46             ` Eli Zaretskii
2014-01-11 19:36           ` Paul Eggert
2014-01-11 20:53             ` Eric S. Raymond
2014-01-11 20:13         ` David Reitter
2014-01-11 20:36           ` David Kastrup
2014-01-11 21:26           ` Eric S. Raymond
2014-01-11 22:22             ` David Reitter
2014-01-11 23:03             ` Converting bzr revision-IDs to action stamps (was: Bazaar references complicate the git transition) Joshua Judson Rosen
2014-01-11 23:45               ` Eric S. Raymond
2014-01-12  5:39                 ` Joshua Judson Rosen
2014-01-12 12:43                   ` Eric S. Raymond
2014-01-11 18:39 ` Bazaar references complicate the git transition Richard Stallman
2014-01-12  3:14   ` Stefan Monnier
2014-01-12  3:55     ` Eric S. Raymond
2014-01-12 22:25       ` Stefan Monnier
2014-01-12 23:02         ` Eric S. Raymond
2014-01-13  2:28         ` Glenn Morris
2014-01-13  3:42           ` Stefan Monnier
2014-01-12 13:44     ` Richard Stallman

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=87zjn2misz.fsf@zigzag.favinet \
    --to=ttn@gnu.org \
    --cc=emacs-devel@gnu.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).