Hi all, I have grown quite fond of bazaar, http://bazaar-vcs.org/. I think g-wrap should switch to using it. To that end, I have imported[0] the main g-wrap branches from arch into bazaar and have published them on my web site:
http://wingolog.org/bzr/g-wrap/ I will paste in the contents of http://wingolog.org/bzr/g-wrap/README: G-Wrap Bazaar Archives ====================== The links in this directory are Bazaar mirrors of the G-Wrap source archive, along with mirrors of some of the developers' archives. The following archives are available: mainline: the mainline archive, from [EMAIL PROTECTED]/g-wrap--dev--0 lcourtes: Ludovic Courtes' branch, from [EMAIL PROTECTED]/g-wrap--devo--2.0 wingo: Andy Wingo's branch, published only via bzr. These mirror archives are provided because I (Andy Wingo) am dissatisfied with GNU Arch, the upstream VCS. I would like people to give bzr a try, because I find it to be both more powerful and easier at the same time. As an introduction to bzr, try: $ bzr get http://wingolog.org/bzr/g-wrap/lcourtes # hack hack hack $ bzr commit -m 'fix the foo' $ bzr push sftp://example.com/home/me/www/my-g-wrap-branch For more information on Bazaar, see http://bazaar-vcs.org/. I have some pending patches for g-wrap which I will publish in my branch there. I will let the mailing list know. In the meantime, folks should take these archives for a test drive, a bzr annotate, a bzr log, etc. Cheers, Wingo. [0] Importing is very easy; just install bzr and bzrtools, then do: $ bzr baz-import-branch where-to-put-bzr-branch/ \ [EMAIL PROTECTED]/g-wrap--dev--0 The same command will update the bzr branch when there are new commits in the arch branch. -- http://wingolog.org/ _______________________________________________ g-wrap-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/g-wrap-dev
