From: Chong Yidong <cyd@stupidchicken.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: Bazaar
Date: Thu, 17 Sep 2009 16:55:50 -0400 [thread overview]
Message-ID: <874or1b8a1.fsf@stupidchicken.com> (raw)
In-Reply-To: <jwvd45ps4by.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 17 Sep 2009 16:40:16 -0400")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> Sorry for not being more clear:
> sftp://bzr.sv.gnu.org/srv/bzr/emacs/emacs-merges is the "shared
> repository" of all branches.
> sftp://bzr.sv.gnu.org/srv/bzr/emacs/emacs-merges/master holds the branch
> that corresponds to the CVS trunk.
>
> But again, don't try to clone directly from there (it takes many hours),
> download a tarball instead (or do a "cp -a" after mounting the
> repository via sshfs, but beware that the core of the data is in
> sftp://bzr.sv.gnu.org/srv/bzr/emacs/emacs-merges/.bzr, so if you only
> copy a branch you'll be sorely disappointed).
Would it make much of a difference if we omit some of those old CVS
branches from the conversion (if that's even possible)? I presume no
one is going to go rooting around the "amigados-merge" branch from 1996.
Even things like the rmail-mbox branch and the emacs-unicode branch
could probably be discarded.
next prev parent reply other threads:[~2009-09-17 20:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-15 17:29 Bazaar Stefan Monnier
2009-09-17 17:47 ` Bazaar Stefan Monnier
2009-09-23 20:09 ` Bazaar Karl Fogel
2009-09-17 18:24 ` Bazaar Chong Yidong
2009-09-17 20:40 ` Bazaar Stefan Monnier
2009-09-17 20:55 ` Chong Yidong [this message]
2009-09-17 22:32 ` Bazaar Andreas Schwab
2009-09-18 1:04 ` Bazaar Stefan Monnier
2009-09-18 8:48 ` Bazaar Eli Zaretskii
2009-09-18 1:17 ` Bazaar Chong Yidong
[not found] ` <87bpl9hsno.fsf@workhorse.earlhome>
2009-09-18 14:02 ` Bazaar Stefan Monnier
2009-09-18 17:35 ` Bazaar Glenn Morris
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=874or1b8a1.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.