Nathaniel Smith [EMAIL PROTECTED] writes:
The merkle trie synchronization algorithm is a set synchronization
algorithm -- given a set of items here and a set of items there,
each with a unique id, it lets each side figure out what it needs to
send so that the other side will end up with
On Wed, Aug 09, 2006 at 08:45:51AM -0700, Steven E. Harris wrote:
Nathaniel Smith [EMAIL PROTECTED] writes:
To make our life simpler, we always send stuff in such an order that
we can simply stream it straight to the db and consistency is always
maintained; that way we can simply hit
Nathaniel Smith [EMAIL PROTECTED] writes:
To make our life simpler, we always send stuff in such an order that
we can simply stream it straight to the db and consistency is always
maintained; that way we can simply hit commit at any time.
So the sender orders items with respect to the
On Sat, Aug 05, 2006 at 12:09:28PM -0700, Steven E. Harris wrote:
Nathaniel Smith [EMAIL PROTECTED] writes:
We simply maintain consistency during a sync -- we don't store a
revision until we have all the files it references, and we don't
store a cert until we have the revision it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan S. Shapiro schreef:
Like monotone, OpenCM does not store entries for directories;
AFAIK that's only true for .25 and earlier, .26 and beyond seem to store
entries for directories as well, since 'mkdir foo ; touch foo/bar ; mtn
add
On 8/4/06, Koen Kooi [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan S. Shapiro schreef:
Like monotone, OpenCM does not store entries for directories;
AFAIK that's only true for .25 and earlier, .26 and beyond seem to store
entries for directories as well,
Koen Kooi wrote:
AFAIK that's only true for .25 and earlier, .26 and beyond seem to store
entries for directories as well, since 'mkdir foo ; touch foo/bar ; mtn
add foo/bar' errors out with 'foo' being unknown (*very* annoying).
Its true that 0.26 and later version directories (and directory
Hallo,
On 8/4/06, Koen Kooi [EMAIL PROTECTED] wrote:
Try:
[EMAIL PROTECTED]:~/OE/monotone/org.openembedded.dev/packages/e17$ mkdir baz
[EMAIL PROTECTED]:~/OE/monotone/org.openembedded.dev/packages/e17$ cd baz/
[EMAIL PROTECTED]:~/OE/monotone/org.openembedded.dev/packages/e17/baz$ touch foo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alex Queiroz schreef:
Hallo,
On 8/4/06, Koen Kooi [EMAIL PROTECTED] wrote:
Try:
[EMAIL PROTECTED]:~/OE/monotone/org.openembedded.dev/packages/e17$ mkdir baz
[EMAIL PROTECTED]:~/OE/monotone/org.openembedded.dev/packages/e17$ cd baz/
[EMAIL
On Fri, 2006-08-04 at 21:24 +0200, Koen Kooi wrote:
Try:
[EMAIL PROTECTED]:~/OE/monotone/org.openembedded.dev/packages/e17$ mkdir baz
[EMAIL PROTECTED]:~/OE/monotone/org.openembedded.dev/packages/e17$ cd baz/
[EMAIL PROTECTED]:~/OE/monotone/org.openembedded.dev/packages/e17/baz$ touch
foo
Koen Kooi [EMAIL PROTECTED] writes:
[...]
Try:
[EMAIL PROTECTED]:~/OE/monotone/org.openembedded.dev/packages/e17$ mkdir baz
[EMAIL PROTECTED]:~/OE/monotone/org.openembedded.dev/packages/e17$ cd baz/
[EMAIL PROTECTED]:~/OE/monotone/org.openembedded.dev/packages/e17/baz$ touch
foo
[EMAIL
On Fri, 2006-08-04 at 21:44 +0200, Thomas Keller wrote:
Hrm... indeed, never noticed that. Exists a bug already for this
misbehaviour?
Since it isn't misbehavior, I hope not. :-)
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
On 8/4/06, Jonathan S. Shapiro [EMAIL PROTECTED] wrote:
On Fri, 2006-08-04 at 21:24 +0200, Koen Kooi wrote:
$ cd baz/
$ touch foo
$ mtn add baz
mtn: misuse: no such file or directory: 'packages/e17/baz/baz'
This is correct. You're trying to add baz/baz, which doesn't exist.
Koen:
Are
Jonathan S. Shapiro [EMAIL PROTECTED] writes:
[...]
Also, the need to sync a 400 kbyte object in order to begin a
checkout is very disconcerting to users -- especially when you are
doing it over a slow link at (e.g.) a hotel or (e.g.) a PPP link
[Yes, a lot of people really still use
On Friday 04 August 2006 21:47 Jonathan S. Shapiro wrote:
mtn path names in the workspace are relative to the current working
directory.
The confusing thing about this is that paths provided by the user on the
command line always have to be relative to the current working directory,
while the
On 8/4/06, Bruce Stephens [EMAIL PROTECTED] wrote:
Jonathan S. Shapiro [EMAIL PROTECTED] writes:
[...]
Also, the need to sync a 400 kbyte object in order to begin a
checkout is very disconcerting to users -- especially when you are
doing it over a slow link at (e.g.) a hotel or (e.g.) a PPP
On Friday 04 August 2006 22:25 Jonathan S. Shapiro wrote:
For example, the mtn status command gives status for
every file in the project. If this output was PWD-relative, you would
get things like:
[M] fred.c
[D] ../baz/mumble.c
which would be confusing. Worse, the answer differs
On Fri, 2006-08-04 at 22:50 +0200, Thomas Moschny wrote:
On Friday 04 August 2006 22:25 Jonathan S. Shapiro wrote:
For example, the mtn status command gives status for
every file in the project. If this output was PWD-relative, you would
get things like:
[M] fred.c
[D]
On Friday 04 August 2006 23:25 Jonathan S. Shapiro wrote:
Try it on a 20,000 file project and then see what you think.
Well, no, I don't expect to easily understand any output 20.000 lines long,
whatever it does look like.
That's what the restrictions are for.
The fact that the output is
On Fri, Aug 04, 2006 at 09:01:12PM +0200, Koen Kooi wrote:
Jonathan S. Shapiro schreef:
Like monotone, OpenCM does not store entries for directories;
AFAIK that's only true for .25 and earlier, .26 and beyond seem to store
entries for directories as well, since 'mkdir foo ; touch
20 matches
Mail list logo
