unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joshua Judson Rosen <rozzin@geekspace.com>
Cc: esr@thyrsus.com, handa@gnu.org, emacs-devel@gnu.org
Subject: Re: Can anyone correct the Bazaar reference "revno:111954.1.97"?
Date: Sun, 02 Mar 2014 19:44:54 +0200	[thread overview]
Message-ID: <83iorwtrzd.fsf@gnu.org> (raw)
In-Reply-To: <87eh2l5kif.fsf@slice.rozzin.com>

> From: Joshua Judson Rosen <rozzin@geekspace.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,  handa@gnu.org,  emacs-devel@gnu.org
> Date: Sat, 01 Mar 2014 22:47:52 -0500
> 
> It does look like the merge (112051) is indeed `just a merge'.
> 
> Actually going through and comparing the diffs ("bzr diff -c 112051"
> vs. "bzr diff -c 11964.1.6"), the diffs off the two revisions are
> identical except for slight differences in context

This is bzr, not git, so the diffs aren't the whole story.  The
arrangement of the parents is also part of it, and it's different.

>     $ bzr log --line -r 112051 -n0
>     112051: K. Handa 2013-03-16 [merge] Optimize ASCII file reading...
>       111964.1.7: K. Handa 2013-03-16 [merge] merge trunk
>       111964.1.6: K. Handa 2013-03-16 Optimize ASCII file reading...
>       111964.1.5: K. Handa 2013-03-11 [merge] merge trunk
> 
> i.e.: the only thing that's at all different between the two
> _changes_ is a slight difference in context, due to their different
> positions in the DAG. Had the "Optimize ASCII file reading..."
> change happened _after_ the second "merge trunk" (11964.1.7)
> instead of before it, then I do think even the diff contexts
> would be the same (the revision that 11964.1.7 was merging into
> Handa's "work" branch was trunk 12050).

Even if the diffs were identical, the revisions won't be.  Not in bzr.




  reply	other threads:[~2014-03-02 17:44 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 [this message]
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
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=83iorwtrzd.fsf@gnu.org \
    --to=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).