unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: Andreas Schwab <schwab@linux-m68k.org>, emacs-devel@gnu.org
Subject: Re: Release tags
Date: Fri, 07 Sep 2012 21:22:26 +0800	[thread overview]
Message-ID: <87zk52q86l.fsf@gnu.org> (raw)
In-Reply-To: <87vcfsjxhu.fsf@wanadoo.es> ("Óscar Fuentes"'s message of "Wed, 05 Sep 2012 17:33:01 +0200")

Óscar Fuentes <ofv@wanadoo.es> writes:

> Jason, try executing `bzr qlog' from your trunk branch checkout and
> click on the small circles that contains a + symbol (those are merge
> revisions.) You will see that a merge revision joins a series of
> revisions from the original branch (trunk, in this case) with a series
> of revisions coming from another branch. All revisions are there.

bzr: ERROR: unknown command "qlog"

I think what you are trying to explain is that bzr's history is
full of confusing non-linear parallel universes.  24.2 never existed on
the trunk as far as history of this universe goes - it was made on a
branch.  But DVCS adherents want the possibility of an alternate
universe where 24.2 is on the history of the trunk. The benefit of this
non-linearity is not at all clear to me.





  reply	other threads:[~2012-09-07 13:22 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-28 16:48 Release tags chad
2012-08-29  2:40 ` Chong Yidong
2012-09-04  0:40   ` Tim Cross
2012-09-04  2:25     ` Óscar Fuentes
2012-09-04  2:29     ` William Stevenson
2012-09-04  2:50       ` Eli Zaretskii
2012-09-04 14:32         ` Jason Rumney
2012-09-04 15:57           ` Óscar Fuentes
2012-09-04 16:04             ` Jason Rumney
2012-09-04 17:47               ` Andreas Schwab
2012-09-05 14:55                 ` Jason Rumney
2012-09-05 15:18                   ` Andreas Schwab
2012-09-05 15:33                     ` Óscar Fuentes
2012-09-07 13:22                       ` Jason Rumney [this message]
2012-09-07 14:35                         ` Eli Zaretskii
2012-09-07 15:27                         ` Stefan Monnier
2012-09-04 18:24               ` Óscar Fuentes
2012-09-04 22:43                 ` Tim Cross
2012-09-05  1:53                   ` Stephen J. Turnbull
2012-09-05  2:34                   ` Óscar Fuentes
2012-09-05  3:07                     ` Stephen J. Turnbull
2012-09-05  3:49                       ` Óscar Fuentes
2012-09-05  5:11                         ` Stephen J. Turnbull
2012-09-05  6:34                           ` Jambunathan K
2012-09-05 12:48                           ` Tim Cross
2012-09-05 16:25                           ` Eli Zaretskii
2012-09-05 16:23                         ` Eli Zaretskii
2012-09-05 16:21                       ` Eli Zaretskii
2012-09-05 17:32                         ` Stephen J. Turnbull
2012-09-05 17:42                           ` Eli Zaretskii
2012-09-05 14:32                     ` Stefan Monnier
2012-09-04 16:57             ` Eli Zaretskii
2012-09-04 16:53           ` Eli Zaretskii
2012-09-05  7:16         ` Glenn Morris

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=87zk52q86l.fsf@gnu.org \
    --to=jasonr@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ofv@wanadoo.es \
    --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 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).