Hi,
Is it intentional that (for example) the command
darcs changes --context --tags=2.0.1
in darcs's own repository prints only the "Context:" header and nothing else?
I get the same results with darcs 2.0.2 and the version just built from the
repository. It works as I would expect, namely printing
Context:
[TAG 2.0.2
David Roundy <[EMAIL PROTECTED]>**20080624012041]
or the like, for the tags 2.0.2 and "working version", but no older ones.
(Probably not coincidentally, those are the two tags that appear in darcs
changes --context | grep TAG).
If this is supposed to happen, is there some other way of getting the same
output style for older tags? I know I can do
darcs get --tag=2.0.1 mydarcsrepo scratch
darcs changes --context --repodir=scratch
but I'd really rather avoid creating the temporary copy if at all possible.
(Background: I'm working with a generic interface to source control systems,
that wants to know the revision ID that it's /going/ to check out before
actually checking it out, and in darcs, the obvious meaning of "revision ID"
is of course the context. If I was always going to be working with tags, I
could just use the tag name, but it could equally well be just "whatever's in
the repository", and I want to be consistent between the two cases.
That's why I don't want to do the extra darcs get just to find the context -
it would be messy to do so, remove the scratch copy, and then immediately
create the copy that I'm going to be working with, and also messy to somehow
turn the scratch copy into the working copy.)
Thanks in advance.
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
