Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Gerhard Fiedler wrote:
> Tony Hoyle wrote:
>
>>> I think the "precise" method would be to use the commit id. AFAIK cvsnt
>>> assigns a unique commit id to every commit. But also AFAIK, this is
>>> only available server-side, to commit support scripts and in the audit
>>> database. So if you have control over the server and can give yourself
>>> (possibly read-only) access to the audit database, you can run a SQL
>>> query or two and retrieve that information.
>> No need to do that, just use the @commitid syntax.
>>
>> eg. cvs -q log -SR -r@{commitID}
>> or cvs diff -r@<{commitID} -r@{commitID}
>
> Interesting, thanks :)
>
> It seems the real command would look like
>
> cvs -q log -SR -r at 8804650d0eb1722
>
> (At least to me this wasn't completely obvious.)
>
> Is there more of this type? Is this somewhere documented? (A search through
> the manual for "commitid" or "commit id" didn't bring up anything
> relevant.)
>
Pretty much anywhere you can use a tag you can use a commitid.. we
probably should compile a list of 'useful' commands like that - it's in
the documentation but you have to know what you're looking for as it's a
bit scattered.
There's the same kind of thing for bugids too except that's normally
done as a separate option (maybe it shouldn't be... for evs there's the
chance to change it).
Tony