[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Creating shared dev branch
From: |
Bill Wohler |
Subject: |
Re: Creating shared dev branch |
Date: |
Sun, 25 Dec 2011 10:28:30 -0800 |
Eli Zaretskii <address@hidden> wrote:
> > Date: Sun, 25 Dec 2011 09:47:51 -0800
> > From: Bill Wohler <address@hidden>
> > Cc: address@hidden
> >
> > The MH-E developers are having a Bug Squashing Party (BSP) on Tuesday,
> > 12/27. Since Emacs has not yet been released, I'd like to create a dev
> > branch for our work which will be merged back into trunk after the Emacs
> > release.
> > [...]
> > Can anyone suggest a comparable recipe for Bazaar?
>
> 100% untested:
>
> bzr branch trunk/ bug-squash/
> cd bug-squash/
> bzr push --remember bzr+ssh://address@hidden/emacs/bug-squash/
>
> From now on, all commits in bug-squash/ will go to the public branch
> on savannah.
>
> (If you don't like the name "bug-squash", change it as you see fit;
> there's nothing magic about it.)
>
> Note that the public branch created by the above commands will NOT be
> a bound branch. If you want a bound branch, like trunk is, you will
> need to "bzr bind" it afterwards.
>
> HTH
It does, indeed! Thanks!
You're fine with me creating a branch called "mh-e" at the top-level
rather than in some sub-directory? There appears to be a directory
called other-branches.
Also, any concerns about the disk space this branch will take (~300 MB)?
--
Bill Wohler <address@hidden> aka <address@hidden>
http://www.newt.com/wohler/
GnuPG ID:610BD9AD