On Mon, Mar 1, 2010 at 10:21 PM, Scott Brozell <sbrozell.rci.rutgers.edu> wrote:
> Hi,
>
> On Sun, Feb 28, 2010 at 10:52:20AM -0300, Gustavo Seabra wrote:
>> I was just wondering... Is there a way to fully specify the version of
>> amber we are talking about when we report an error? I mean, is there a
>> (CVS?) command that uniquely identify the state of the distribution we
>> are working on? I know, for example, that whenever there's a change,
>> svn changes the tag for every file in the distribution to a new
>> number, so it's always possible to uniquely identify the version we
>> are referring to. Is there a similar thing in CVS?
>
> There's no short way like in svn or git.
> You could follow my suggestion from a few days ago and use the date
> from the make install:
> Starting installation of AmberTools, version 1.3 at Mon Sep 21 01:58:49 EDT 2009.
> since cvs can update to a date:
> a cvsld 'cvs log -d "\!*" | less "+G?selected revisions: [1-9]"'
> #cvs log -d "04/10/2003>03/31/2003" | less '+G?selected revisions: [1-9]'
>
> Another idea is to capture the output of
> cvs status
> but this is a verbose approach.
>
> Scott
Thanks,
Gustavo Seabra
Professor Adjunto
Departamento de Química Fundamental
Universidade Federal de Pernambuco
Fone: +55-81-2126-7450 Ext. 5021
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Mon Mar 01 2010 - 18:30:05 PST
