From: Eli Zaretskii <eliz@gnu.org>
To: Xavier Maillard <xma@gnu.org>
Cc: dann@ics.uci.edu, emacs-devel@gnu.org
Subject: Re: Listing branches with bzr
Date: Thu, 03 Dec 2009 05:55:51 +0200 [thread overview]
Message-ID: <83einclni0.fsf@gnu.org> (raw)
In-Reply-To: <200912022324.nB2NOON2007714@fed.local>
> Date: Thu, 3 Dec 2009 00:24:24 +0100
> From: Xavier Maillard <xma@gnu.org>
> CC: dann@ics.uci.edu, emacs-devel@gnu.org
> Jabber-ID: xavier@maillard.im
>
>
> > Date: Tue, 1 Dec 2009 14:00:29 -0800 (PST)
> > From: Dan Nicolaescu <dann@ics.uci.edu>
> > Cc: emacs-devel@gnu.org
> >
> > Eli Zaretskii <eliz@gnu.org> writes:
> >
> > > Is there a bzr command to show all the branches in the master
> > > repository? I couldn't find such a command. "bzr tags" comes the
> > > closest, but it only shows the tags that were used to start each
> > > branch, not the branch names.
> >
> > If you find a command/set of commands that do this, then we can add a
> > vc-bzr function to do it, and bind it to the vc and vc-dir menu.
>
> Seems like "bzr branches" is it, although I didn't yet try it.
>
> Note that this command is not part of the default GNU Bazaar
> distribution but is in the bzrtools package.
Yes, I understand. But bzrtools is generally considered as a
must-have; e.g., the Windows installer installs it by default.
Perhaps VC Mode should suggest installing it if the command brings an
error, though.
next prev parent reply other threads:[~2009-12-03 3:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 19:06 Listing branches with bzr Eli Zaretskii
2009-12-01 21:46 ` Karl Fogel
2009-12-01 21:57 ` Xavier Maillard
2009-12-01 22:20 ` Jason Earl
2009-12-02 1:57 ` Lennart Borgman
2009-12-02 2:13 ` Óscar Fuentes
2009-12-02 2:17 ` Lennart Borgman
2009-12-02 2:44 ` Óscar Fuentes
2009-12-02 3:53 ` Stephen J. Turnbull
2009-12-02 6:21 ` Eli Zaretskii
2009-12-02 13:45 ` Martin Albisetti
2009-12-01 21:55 ` Stefan Monnier
2009-12-01 22:00 ` Dan Nicolaescu
2009-12-02 4:19 ` Eli Zaretskii
2009-12-02 23:24 ` Xavier Maillard
2009-12-03 3:55 ` Eli Zaretskii [this message]
2009-12-01 22:08 ` Alexander Belchenko
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=83einclni0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=xma@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).