[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bazaar workflow for GRUB
From: |
Colin Watson |
Subject: |
Re: Bazaar workflow for GRUB |
Date: |
Tue, 19 Jan 2010 11:04:55 +0000 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Tue, Jan 19, 2010 at 09:57:07AM +0530, BVK Chaitanya wrote:
> On Mon, Jan 18, 2010 at 11:45 PM, Colin Watson <address@hidden> wrote:
> > I recommend using a checkout for trunk, because that way bzr takes out a
> > write lock on the branch when you start committing and doesn't release
> > it until it's finished; it also warns you immediately if you're out of
> > date rather than making you commit and try to push before you find out.
> > This is a much more robust workflow for shared branches in my
> > experience.
>
> These are the exact features I want for the trunk branch. How
> different is a checkout from a branch?
The best answer is probably to point you at 'bzr help checkouts'.
> Can i create feature *branch*es from a *checkout*, like in:
>
> bzr checkout sftp://address@hidden/srv/bzr/grub/trunk/grub trunk
> bzr branch trunk feature-foo
Yes.
> How different would such a feature branch be, from regular branch?
No difference.
--
Colin Watson address@hidden