monotone-devel
[Top][All Lists]
Advanced

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

[Monotone-devel] Re: default branch for "monotone sync"


From: Lapo Luchini
Subject: [Monotone-devel] Re: default branch for "monotone sync"
Date: Sat, 24 Feb 2007 21:28:31 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050908 Thunderbird/1.4 Mnenhy/0.7.4.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Evan Martin wrote:
> Am I doing something wrong here, or is this expected behavior? (In the
> latter case, is it desirable?)

It is in fact expected (whether it is desirable or not, is debatable).
The "best way to go" depends on your use case:
a. --set-default all the branches you use, and sync everyone of them at
every sync (not desirable if you have different branches accepted only
on different servers)
b. use a different database for each project: each database has his own
defaults regarding server and branches to push/pull/sync

"sync" does not use the "workspace branch" as a default because sync'ing
a single branch is usually NOT what you want to: it is sometimes less
efficient to do so.
Example:
revision 1 is on branch A
revision 2 is on branch B and is a child of revision 1
if you "sync server A" you send revision 1 only if missing
if you "sync server B" you send revision 2 only if missing, and revision
1 IN ANY CASE (the server is filtering on branch B and can't possibly
know in advance that you're sending a branch B revision whose parent is
in a different parent)
OTOH if you "sync server A B" or "sync server *" the server has
"knowledge" of branch A too, and revision 1 is not sent unnecessarily.

PS: this is efficiency, not correctness: after having received it the
remote server knows that revision 1 was already locally known and
ignores it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQIcBAEBAgAGBQJF4J/vAAoJELBiMTth2oCDCTQQAIQYBTXXNgYmODiCbEgBhUYQ
hX6bIYX5Wpf7b2NXPDDgAzBUH0ObEY00JM/mKwyod6hPX+8KD1aWIzQWcEBCtBWM
sy1T1CtMjUqof4n3wCz+zvBL6QqCxbFaC6IuFi01zUI8ovjzf7dw6K/niaJmtrZd
uCcLwzx/aeOOCXelF3albMG4nVZ5DZL2w6WXyPQnbpmNpC5xyXVmid9w8lBfA4vB
T4/z0T7o/bAN71GBVhYHkEeGdGeKA5+yd3UwfM2CT8rEAtJTEcwcdwk+OPc6OyZA
bhc9BUFM9rH/d5qbZozxKmeGnG/CCr+Px6DIzM17umqvEP52VnyObbNY/3K3LrXs
OyBsenzfjCnQ8h35pmZswPYxKqCjIJS+Gh/wxbL9oLsPP0FQQDC8pCvtwrORKlNb
di6rOS5BT0ejvVYNNp8ukERhA+3+Q/cdkMfUPfWNM+r6O3E+9aAvgaTr705JZzL0
uJzqlAoY53RtqlzwPtpt6Z1TgL2wMUwnhXwy7+qQj+DSkOkqdKIbTU8QsbIiOd5G
nNQ7QtP5ByaHmtQUeKqn8G096xXfssSLuah/m2bVVJiksC/LXSviulVg7u+Dmk2W
6diKJt1uZ/EFVZsmb5RxCQooPsDFXggTzFLmyhdUP8UHlFOQvsImobVTulPcNZxm
pEUQaN1s99wkgcw8nvIn
=awqK
-----END PGP SIGNATURE-----





reply via email to

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