unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: schwab@linux-m68k.org, emacs-devel@gnu.org
Subject: Re: `about-emacs' - what about the revno?
Date: Wed, 01 Sep 2010 09:45:22 +0200	[thread overview]
Message-ID: <jwv39ttc3jw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1Oqh1s-00033i-4v@fencepost.gnu.org> (Eli Zaretskii's message of "Wed, 01 Sep 2010 02:42:40 -0400")

>> >> You search for "http emacs bzr trunk" and voilà:
>> >> http://bzr.savannah.gnu.org/r/emacs/trunk
>> > There's an easier way: in .bzr/branc/branch.conf we have this line:
>> >   parent_location = ../trunk/
>> The parent branch of my main work branch is not "trunk", so while this
>> may work for your particular workflow, it won't DTRT for all workflows.
> But then what exactly is the definition of "ancestor"?  I took it in
> bzr terms for the current branch, but now it seems you had something
> different in mind.  What is it?

The same definition as the one for "-r ancestor:...", i.e. an ancestor
of the current revision is a revision that's part of the current
revision's history.

And what I want is the nearest ancestor that's on one of the branches
hosted in bzr.sv.gnu.org.  And for convenience's sake, I'd like this
ancestor to be described not by a revision-id but by a "branchname+revno".


        Stefan



  reply	other threads:[~2010-09-01  7:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-28 15:38 `about-emacs' - what about the revno? Drew Adams
2010-08-28 15:57 ` Eli Zaretskii
2010-08-28 16:05   ` Drew Adams
2010-08-28 16:13     ` Eli Zaretskii
2010-08-28 16:34     ` Jason Rumney
2010-08-28 17:12   ` Óscar Fuentes
2010-08-28 19:06   ` Christoph
2010-08-29  4:56   ` Teemu Likonen
2010-08-30 15:41   ` Stefan Monnier
2010-08-30 16:22     ` Lennart Borgman
2010-08-30 16:27     ` Eli Zaretskii
2010-08-30 17:50       ` Eli Zaretskii
2010-08-30 19:20         ` Óscar Fuentes
2010-08-30 22:07           ` Stefan Monnier
2010-08-31  6:34         ` Andreas Schwab
2010-08-31 10:35           ` Stefan Monnier
2010-08-31 10:41             ` Andreas Schwab
2010-08-31 13:01               ` Stefan Monnier
2010-08-31 20:08                 ` Óscar Fuentes
2010-09-01  6:20                   ` Stefan Monnier
2010-08-31 14:02               ` Miles Bader
2010-08-31 16:56             ` Eli Zaretskii
2010-09-01  6:25               ` Stefan Monnier
2010-09-01  6:42                 ` Eli Zaretskii
2010-09-01  7:45                   ` Stefan Monnier [this message]
2010-09-01  8:41                     ` Eli Zaretskii
2010-08-31 16:58             ` Eli Zaretskii
2010-08-30 17:39     ` Óscar Fuentes
2010-08-30 17:58       ` Lennart Borgman
2010-08-30 22:08       ` Stefan Monnier
2010-08-30 22:45         ` Óscar Fuentes
2010-08-31  8:22           ` Stefan Monnier

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=jwv39ttc3jw.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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).