On Wed, Nov 26, 2008 at 7:59 PM, Conal Elliott <[EMAIL PROTECTED]> wrote:
> Hi Trent, > > I have mostly darcs-1 repos. Perhaps just one darcs-2, according to 'darcs > show repo'. For instance, > > [EMAIL PROTECTED]:~/Haskell/reactive$ darcs show repo > Type: darcs > Format: darcs-1.0 > Root: /home/conal/Haskell/reactive > Pristine: PlainPristine "_darcs/pristine" > Cache: thisrepo:/home/conal/Haskell/reactive > Default Remote: [EMAIL PROTECTED]:/srv/code/reactive > Num Patches: 270 > > Am I likely to get better performance by converting my repo to darcs-2 > format? You could try it. You could convert a copy of the repo and see if it's better. I wish I had some data on this but I don't. Darcs2 format is a big win in terms of robustness but it can be slower for certain operations. In your case I don't know if it will help. > From the darcs manual, it looks like my friends are "darcs convert d1repo > d2repo" and "darcs init --darcs2" for new projects. I've placed "init > darcs2" in my ~/.darcs/defaults, which seems to do the trick. I also see > some advanced options to 'darcs convert', particularly -ssh-cm and > -http-pipelining. Is either of those options relevant to my problem? Oh hrm. If --ssh-cm and --http-pipelining are showing up in convert that's probably a bit of a bug. As far as I know, those only affect connections and are not a persistent settings. Once I convert a repo to darcs2 format, do I simply push to the server, or > do I have to start over with a put? When you convert a repository you create a new branch that is not allowed to share patches with any existing branch. This is because the meaning of the patches in the new converted branch can be subtly different compared to the same patches in the old darcs1 branches. Additionally, the meaning depends on the order that the patches are in the repo before the convert, so you should not convert two copies of the repository and then try to use them together -- doing so could lead to serious corruption. In essence, when you're ready to convert from darcs1 to darcs2, you have to do it once per project and be prepared to throw away all copies of the darcs1 repo. Expect to coordinate with your users/contributors. I wish we could make this easier. For your case of testing, you could just convert a copy and try it, then deleted the darcs2 copy if you don't like the results. Thanks, Jason
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
