All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Watson <cjwatson@ubuntu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Personal branches in Bazaar repository
Date: Sat, 24 Oct 2009 15:31:30 +0100	[thread overview]
Message-ID: <20091024143127.GD28534@riva.ucam.org> (raw)
In-Reply-To: <20091024132025.GA29975@thorin>

On Sat, Oct 24, 2009 at 03:20:25PM +0200, Robert Millan wrote:
>   bzr branch sftp://${username}@bzr.savannah.gnu.org/srv/bzr/grub/trunk/
>   # hack
>   bzr commit
>   bzr push --remember sftp://${username}@bzr.savannah.gnu.org/srv/bzr/grub/people/${username}
> 
> If they prefer a Subversion-like workflow (i.e. commit implies push), they can
> checkout the branch afterwards:
> 
>   bzr checkout sftp://${username}@bzr.savannah.gnu.org/srv/bzr/grub/people/${username}
> 
> and work basically the same as they would in Subversion.

Just another detail which may be useful: if you've done the former
(branch, push) and want to convert it into the latter (checkout) without
having to fetch the branch again from scratch, then you can do this:

  bzr bind :push

This converts the local branch into a checkout of the remembered push
location.


I would also generally recommend using bzr+ssh:// rather than sftp://
URLs. sftp:// involves copying all the metadata back and forward for a
number of operations. bzr+ssh:// runs a smart server on the remote
system and interacts with that, which is generally much faster. If you
do this, you'll need to drop /srv/bzr from the URL as well, so:

  bzr branch bzr+ssh://${username}@bzr.sv.gnu.org/grub/trunk


Although I'm not a Bazaar developer myself, I have a lot of experience
with using it, and am happy to offer assistance to any GRUB developers
who may run into problems.

-- 
Colin Watson                                       [cjwatson@ubuntu.com]



      reply	other threads:[~2009-10-24 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-24 13:20 Personal branches in Bazaar repository Robert Millan
2009-10-24 14:31 ` Colin Watson [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091024143127.GD28534@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.