unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: esr@thyrsus.com, handa@gnu.org, emacs-devel@gnu.org,
	Joshua Judson Rosen <rozzin@geekspace.com>
Subject: Re: Can anyone correct the Bazaar reference "revno:111954.1.97"?
Date: Sun, 02 Mar 2014 19:26:46 +0100	[thread overview]
Message-ID: <871tykihi1.fsf@igel.home> (raw)
In-Reply-To: <83iorwtrzd.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 02 Mar 2014 19:44:54 +0200")

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.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



  reply	other threads:[~2014-03-02 18:26 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 [this message]
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
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

  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=871tykihi1.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=esr@thyrsus.com \
    --cc=handa@gnu.org \
    --cc=rozzin@geekspace.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.
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).