unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mike Mattie <codermattie@gmail.com>
To: emacs-devel@gnu.org
Subject: the bzr switchover, how I got up to speed with bzr
Date: Sun, 29 Mar 2009 13:44:26 -0700	[thread overview]
Message-ID: <20090329204425.GA6511@reforged> (raw)

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

Hi,

I read the discussion on the bzr switchover and I wanted to share
my experience with using bzr.

Before Bzr I used svn exclusively. To learn bzr I started off
using it in conjuction with svn. In fact I still do.

What I did is create a shared repository with a subversion
checkout of my project in it. I was then able to use
bzr to create "focused patches".

I learned how to use feature branches, shelve, and the
differences between commit,push, bound branches etc.

I would suggest to the developers who want to get
the hang of bzr before a flag day that this approach of
using bzr in conjunction with the existing RCS system (CVS)
is enormously beneficial.

In retrospect it was far better than doing a flag day and fumbling
with the learning curve. I knew I would botch things while I was
learning the ropes and I was able to scratch a few repositories after
some novice botches.

A tip from the peanut gallery for what it is worth.

Cheers,
Mike Mattie

-- 
GnuPG Key: B9012279 is available from HKP server pgp.mit.edu

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2009-03-29 20:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-29 20:44 Mike Mattie [this message]
2009-03-31  0:40 ` the bzr switchover, how I got up to speed with bzr Karl Fogel
2009-03-31  2:34   ` Mike Mattie

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=20090329204425.GA6511@reforged \
    --to=codermattie@gmail.com \
    --cc=emacs-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.
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).