Timothy Brownawell [EMAIL PROTECTED] writes:
automate inventory is printing birth revisions for ignored files, which
breaks the automate_inventory test. The automate_inventory_restricted
test is also failing, which at first glance looks to be due to the same
problem.
These tests are passing
On Sun, 2008-06-01 at 04:37 -0400, Stephen Leake wrote:
Timothy Brownawell [EMAIL PROTECTED] writes:
automate inventory is printing birth revisions for ignored files, which
breaks the automate_inventory test. The automate_inventory_restricted
test is also failing, which at first glance
automate inventory is printing birth revisions for ignored files, which
breaks the automate_inventory test. The automate_inventory_restricted
test is also failing, which at first glance looks to be due to the same
problem.
___
Monotone-devel mailing
Stephen Leake wrote:
Derek Scherger [EMAIL PROTECTED] writes:
At a glance the docs look reasonable. I'm still not sure I prefer the
old_path and new_path stuff over the node id's though.
It's a compromise. Can you live with it?
You guys have more experience with it than I do at this point
Derek Scherger [EMAIL PROTECTED] writes:
Thomas Keller wrote:
Looks good. I did some small tweaks on the command line and version
display, but the rest seems to be fine. Just one thing hit my eyes:
Full support for versioned directories is not yet complete and the
inventory will only list
Derek Scherger [EMAIL PROTECTED] writes:
I vaguely recall some mention of a restricted inventory case where only
one side of a rename was listed in the inventory. Is there a test for
this?
Yes; see tests/automate_inventory_restricted/__driver__.lua, search
for the comment:
-- Rename a file
Derek Scherger [EMAIL PROTECTED] writes:
At a glance the docs look reasonable. I'm still not sure I prefer the
old_path and new_path stuff over the node id's though.
It's a compromise. Can you live with it?
Also, I see a FIXME in the docs for the invalid status
Yes, it needs a test. But
Stephen Leake schrieb:
Derek Scherger [EMAIL PROTECTED] writes:
I vaguely recall some mention of a restricted inventory case where only
one side of a rename was listed in the inventory. Is there a test for
this?
Yes; see tests/automate_inventory_restricted/__driver__.lua, search
for the
Stephen Leake schrieb:
I updated the automate inventory section in monotone.texi; I believe
it matches the code.
Looks good. I did some small tweaks on the command line and version
display, but the rest seems to be fine. Just one thing hit my eyes:
Full support for versioned directories is
Thomas Keller wrote:
Looks good. I did some small tweaks on the command line and version
display, but the rest seems to be fine. Just one thing hit my eyes:
Full support for versioned directories is not yet complete and the
inventory will only list entries for renamed or dropped directories.
I vaguely recall some mention of a restricted inventory case where only
one side of a rename was listed in the inventory. Is there a test for
this? Is it still a problem?
I wonder if this case is the one that is fixed in the
net.venge.monotone.experiment.restricted_rosters branch. BTW, has anyone
At a glance the docs look reasonable. I'm still not sure I prefer the
old_path and new_path stuff over the node id's though.
Also, I see a FIXME in the docs for the invalid status and the name of
this status value could probably be improved, invalid was simply the
first thing I thought of when I
Richard Levitte [EMAIL PROTECTED] writes:
In message [EMAIL PROTECTED] on Wed, 05 Sep 2007 17:31:59 -0400, Stephen
Leake [EMAIL PROTECTED] said:
stephen_leake I was waiting for the 0.36 release to be done to raise
stephen_leake this issue again, and then I was waiting for time to
Stephen Leake wrote:
I haven't heard any objections to this; a couple people said they
would review the docs and such.
So if I have not heard any objections by this weekend (Sept 15), I'll
merge nvm.basic_io.inventory to nvm then.
Ok?
I haven't had a chance to read the docs on the
Derek Scherger [EMAIL PROTECTED] writes:
Stephen Leake wrote:
I haven't heard any objections to this; a couple people said they
would review the docs and such.
So if I have not heard any objections by this weekend (Sept 15), I'll
merge nvm.basic_io.inventory to nvm then.
Ok?
I haven't
Nathaniel Smith [EMAIL PROTECTED] writes:
I get the impression that the inventory fixes, for instance, are just
stalled because everyone is nervous there are things they haven't
thought of and that could be arbitrarily bad, I mean who *knows* what
you haven't thought of, you certainly
In message [EMAIL PROTECTED] on Wed, 05 Sep 2007 17:31:59 -0400, Stephen
Leake [EMAIL PROTECTED] said:
stephen_leake I was waiting for the 0.36 release to be done to raise
stephen_leake this issue again, and then I was waiting for time to
stephen_leake write those few more tests. But I think it
Richard Levitte wrote:
In message [EMAIL PROTECTED] on Wed, 05 Sep 2007 17:31:59 -0400, Stephen
Leake [EMAIL PROTECTED] said:
stephen_leake I was waiting for the 0.36 release to be done to raise
stephen_leake this issue again, and then I was waiting for time to
stephen_leake write those
Nathaniel Smith wrote:
Umm, Derek? 'automate' is where we're supposed to actually care about
compatibility -- that we happened to tweak the changeset format is
fine, but I'm sure the connection between that and the inventory
output format is not obvious to people implementing 3rd-party tools,
Nathaniel Smith wrote:
compatibility -- that we happened to tweak the changeset format is
fine, but I'm sure the connection between that and the inventory
output format is not obvious to people implementing 3rd-party tools,
and this is something that would be have pretty trivial to keep the
Daniel THOMPSON wrote:
Hi Folks
Recently upgraded to and started using in earnest a post-rosters version
of monotone (0.28). Everything is going pretty well but it appears that
the behavior of 'automate inventory' has changed since the last version
I used (0.25) and this has causes knock on
Hi Folks
Recently upgraded to and started using in earnest a post-rosters version
of monotone (0.28). Everything is going pretty well but it appears that
the behavior of 'automate inventory' has changed since the last version
I used (0.25) and this has causes knock on problems with clients of
On Sunday 09 April 2006 23:53, Derek Scherger wrote:
Is anyone actually using inventory in its current form?
I use it to deduce what files have been moved and renamed in maildirs.
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
I've been playing around with automate inventory a bit lately to try and
make the implementation a bit more roster friendly and fix a couple of
small-ish issues.
For reference the current format is (roughly):
column 1: pre-state
unchanged, dropped, renamed from
column 2: post-state
24 matches
Mail list logo
