[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bzr repository ready?

From: Stephen J. Turnbull
Subject: Re: bzr repository ready?
Date: Tue, 24 Nov 2009 03:06:33 +0900

Stefan Monnier writes:

 > >     "emacs" trunk branch).  I think it's worth planning for that
 > >     possibility in structuring the Emacs Bazaar repository.
 > You mean the main repository should not be directly at .../srv/bzr/emacs
 > but at .../srv/bzr/<something>/emacs ?  I think I agree.

I'm not entirely sure what I mean.  I've pretty well convinced myself
there's no big efficiency issue in having "sandbox" branches in with
the emacs-repo tarball, but maybe you want the tarball to omit their
directories (as well as being treeless).

 > I can think of only 3 useful starting points:
 > 1- lightweight checkout: for people who only want to fetch the latest
 >    code but will never need/want the diff/log or contribute code.

This is easy (although we haven't written it up yet).

 > 2- bound branch (aka heavyweight checkout): for people who are happy
 >    with CVS and will never want to create a local branch.

I don't think bound branches should be encouraged in Emacs.  YMMV, but
I think in most loosely organized projects they're a worst practice.

 > 3- a local mirror-branch + a local dev branch.
 > If you want something fancier than (3), read the Bzr docs.

Well, Karl already added a description of feature branching, and I've
done a bit of work on that too.  (In fact, the editorial equivalent of
open heart surgery -- as academic acknowledgments say, "any remaining
badness is all mine", you can't blame Karl.)

I'm reasonably satisfied that it would not be a waste of your time to
review it at this point (and I'm looking forward to Eli's opinion, I'm
hoping he'll find it useful).

 > I'm not actually convinced that (1) and (2) are really that important,
 > so maybe we could drop one of them (or maybe both of them even).
 > But the hard part is to integrate those 3 starting points with the
 > "wget+untar" approach.

Well, if you want that added to the wiki, it's not hard to explain how
to move any local changes from either a checkout or a branch into a
new shared repo.  I'm kinda hoping that people will follow
instructions, and not go in for target practice on their feet---it
should be unnecessary.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]