[Clam-devel] launchpad

Pau Arumí parumi at iua.upf.edu
Tue Aug 5 15:23:20 PDT 2008

On dc, 2008-08-06 at 00:05 +0200, Pau Arumí wrote:
> > I said "almost"  because so far, svn has been imported from a dump file.
> > Now we are waiting for updating to HEAD
> Now it's updated -- thanks Michael Hudson, the launchpad devel/operator
> who has been very helpful
> https://code.launchpad.net/clam
> The web-based diff viewer (also useful for proposed patch/branch merges)
> is very nice -- similar to the one in track .
> Now imagine you prepare a patch to commit to clam, but you want to
> commit locally in small steps. Easy, create the bzr branch 
> $ bzr branch lp:clam
> and do the usual commit operations.
> Now if you want to incorporate latest changes from svn (via our synched
> branch):
> $ bzr merge
> To produce the final patch just "bzr diff". 
> But you don't ever have to send a patch, since you can publish the
> branch.
> But of course you can do more than producing a patch. You can commit all
> the patch history, and even "clean" the patch history, as Andy Wingo
> (BTW, a neighbor of mine, here in Barcelona) comments: 
> http://wingolog.org/archives/2007/12/17/convert-a-bazaar-repository-to-a-set-of-patches
> Well, this will be done better with the bzr-svn plugin -- but it needs
> experimentation...)

Sorry, Wingo blog solution seems to be necessary only for CVS.
Commiting/merging patches/branches to SVN seems super easy.

A CLAM commiter have a branch "bounded" to the svn. Then just merge
patches to his bounded branch and commit. The changes are mirrored to
svn. More here: 


> The 5 min guide to bzr (that Hernan pointed out before)
> http://doc.bazaar-vcs.org/latest/en/mini-tutorial/index.html
> Enjoy
> P
> _______________________________________________
> Clam-devel mailing list
> Clam-devel at llistes.projectes.lafarga.org
> https://llistes.projectes.lafarga.org/cgi-bin/mailman/listinfo/clam-devel

More information about the clam-devel mailing list