[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: List of files committed on a branch
From: |
Murugaiyan, Natarajan [IT] |
Subject: |
RE: List of files committed on a branch |
Date: |
Mon, 10 May 2004 18:02:18 -0400 |
With cvs compiled from latest sources, I am able to get the list
of files committed on a branch using the 'cvs log' command.
Larry mentioned in an earlier post that
You should always tag the branch point when you create a branch.
What is the motivation behind creating a branch point tag when branching?
I could get the list of files using the 'cvs log' command without specifying
the branch point tag.
Any cases where the branch point tag comes in handy?
Natarajan Murugaiyan(Ravi)
-----Original Message-----
From: Larry Jones [mailto:address@hidden
Sent: Monday, May 10, 2004 1:10 PM
To: Murugaiyan, Natarajan [IT]
Cc: address@hidden
Subject: Re: List of files committed on a branch
Murugaiyan, Natarajan [IT] writes [quoting me]:
>
> > cvs -q log -SR -rPROD_BRANCH
>
> The above command does not reference the tag for the branch point.
You said you didn't have a tag for the branch point. And it doesn't
need it -- when you give -r a branch name, it only shows revisions on
the branch.
> Also, the -S option is not supported by version 1.10 of cvs(on Solaris 2.6
> box)
> which I am using.
Then you need to upgrade.
> The above command instead of producing empty list, listed all files in the
> repository.
That's why you need -S. Without it, you get the header for every file,
reguardless of whether you've selected any revisions or not. -S
suppresses the header when there are no selected revisions.
-Larry Jones
I never get to do anything fun. -- Calvin