From: Colin Watson <cjwatson@ubuntu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Bazaar workflow for GRUB
Date: Tue, 19 Jan 2010 11:04:55 +0000 [thread overview]
Message-ID: <20100119110455.GZ5847@riva.ucam.org> (raw)
In-Reply-To: <d019d53c1001182027l402dddf9u75efa6e70539a73@mail.gmail.com>
On Tue, Jan 19, 2010 at 09:57:07AM +0530, BVK Chaitanya wrote:
> On Mon, Jan 18, 2010 at 11:45 PM, Colin Watson <cjwatson@ubuntu.com> 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://bvk@bzr.sv.gnu.org/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 [cjwatson@ubuntu.com]
next prev parent reply other threads:[~2010-01-19 11:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 9:31 Bazaar workflow for GRUB BVK Chaitanya
2010-01-14 20:19 ` Bruce Dubbs
2010-01-18 17:49 ` Colin D Bennett
2010-01-18 18:15 ` Colin Watson
2010-01-18 20:48 ` Colin D Bennett
2010-01-19 22:40 ` Robert Millan
2010-01-19 4:27 ` BVK Chaitanya
2010-01-19 11:04 ` Colin Watson [this message]
2010-01-19 4:21 ` BVK Chaitanya
2010-01-19 10:52 ` Michal Suchanek
2010-01-19 14:49 ` Colin D Bennett
2010-01-19 14:59 ` Michal Suchanek
2010-01-19 23:09 ` Robert Millan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100119110455.GZ5847@riva.ucam.org \
--to=cjwatson@ubuntu.com \
--cc=grub-devel@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.