[Top][All Lists]

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

Re: [Arx-users] How does tag work?

From: Walter Landry
Subject: Re: [Arx-users] How does tag work?
Date: Sat, 27 Nov 2004 19:45:45 -0500 (EST)

Kevin Smith <address@hidden> wrote:
> Walter Landry wrote:
> > Are you sure you ran commit?  I get the exact same errors if I try
> > these things and I have not commited waldron-initial.
> Well, I thought I had. But I just tried a commit and got:
> address@hidden waldron $ arx commit -s "After initial week"
> Problems with a filesystem call
> boost::filesystem::rename
> ,,commit.20041127T185853/++cache/,,removed-by-dopatch-2004-11-27T18:58:54/,,added-119
> ,,commit.20041127T185853/++cache/_arx

Hmm.  That is odd.  It would be good to know how you got into that
situation.  Do you have a shell history that shows how you got there?

> So I figured I would start over...
> address@hidden waldron $ rm -R _arx
> address@hidden waldron $ arx init-tree waldron.initial
> address@hidden waldron $ dir
> ,,manifest.20041127T185854  docs/     lib/      simlinux/ 
> address@hidden waldron $ rm ,,manifest.20041127T185854
> address@hidden waldron $ arx commit -s "After initial week"
> There is an inventory id for this path, but the path itself does not exist.
>          ,,manifest.20041127T185854
> Doh! Apparently I'm not allowed to delete that silly ,, file that I 
> never wanted in the first place.

Actually, if you had deleted it with "arx rm", or used "rm" before the
"init-tree", then it would have worked fine.  The problem is that the
init-tree "add"ed it.

> I tried the whole thing again, but left the ,, file this time, and
> it all seemed to work. Except that the "tag" it created looks
> nothing like a CVS tag. At a minimum, I would suggest that you
> document some "best practices" for how to name tags.

Hmm.  I had forgotten how annoying CVS is.  Tags in CVS are used in
different ways than in ArX.  In CVS, they are the only way to mark a
particular tree-state.  Such a facility is not needed as much in ArX,
since every tree state can be retrieved easily.  Tags in ArX are used
when you want to have a separate branch that marks only major changes.
I believe that is explained in the manual in section 5.9.1.

However, I am planning to coalesce the functionality of tag and config
into a single command (fixing bug #10297).  Essentially, tag would
reduce to the trivial case of a configuration where you only have the
main project.  In that case, I might use a completely different
command, like "aka", "group", "mark", "consolidate", "combine",
"symlink", "pseudonym", or something else (my favorite right now is

> > In any case, I have improved the error messages.  
> Cool. Thanks.

Actually, I decided that the "diff" should have worked anyway.
arx.2.1,103 fixes that.


reply via email to

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