From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: nickrob@snap.net.nz, emacs-devel@gnu.org
Subject: Re: Listing branches in bzr
Date: Fri, 22 Jan 2010 09:41:47 +0200 [thread overview]
Message-ID: <83r5pi7fic.fsf@gnu.org> (raw)
In-Reply-To: <87vdeuhqbq.fsf@stupidchicken.com>
> From: Chong Yidong <cyd@stupidchicken.com>
> Date: Thu, 21 Jan 2010 20:38:01 -0500
> Cc: emacs-devel@gnu.org
>
> nickrob@snap.net.nz (Nick Roberts) writes:
>
> > We've now got bzr which allows easier branching but all I've done is
> > commit to trunk. BzrForEmacsDevs appears to describe creating local
> > branches but how about branches on bzr.savannah.gnu.org? Are there
> > any?
>
> Not yet, but Real Soon Now.
You are probably talking about post-23 branches. Because older
branches inherited from CVS are already there, and there are quite a
few of them.
> (Stefan and I have more or less hashed our plans out, but I'll let
> him explain the details...)
That's good to hear, thanks.
prev parent reply other threads:[~2010-01-22 7:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 22:39 Listing branches in bzr Nick Roberts
2010-01-21 23:48 ` Óscar Fuentes
2010-01-22 0:01 ` Lennart Borgman
2010-01-22 1:44 ` Óscar Fuentes
2010-01-22 0:49 ` Nick Roberts
2010-01-22 1:34 ` Óscar Fuentes
2010-01-22 3:58 ` Nick Roberts
2010-01-22 7:52 ` Eli Zaretskii
2010-01-22 13:08 ` James Cloos
2010-01-22 2:06 ` Glenn Morris
2010-01-22 2:21 ` Nick Roberts
2010-01-22 15:34 ` Stefan Monnier
2010-01-22 1:38 ` Chong Yidong
2010-01-22 7:41 ` Eli Zaretskii [this message]
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=83r5pi7fic.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
/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).