Thanks! The thread comes to an end now! Thanks for bearing with me.
Cheers, Gaurav Vaish http://gallery.mastergaurav.org -------------------------------- On Wed, 27 Oct 2004 04:08:57 -0700, Mark D. Baushke <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Gaurav Vaish <[EMAIL PROTECTED]> writes: > > > > > Let me know if whatever I've understood is > > > > correct or not. > > > > > > Looks like you do so far. > > > > Great! > > > > One last query. After I've commited some files in the branch_name, > > how do I get the latest revision of the same? > > cvs update > > > > Will "cvs co -b branch_name module" give me the latest revision on > > the branch? If so, how do I get the revision on which the branch was > > created? > > It is typically a good idea to create a version tag at the same time as > you create the branch tag. Something like this: > > cvs tag branch_name_BP > cvs tag -b branch_name > > which will allow you to always know what you have put into the > branch_name branch using a simple > > cvs diff -up -rbranch_name_BP -rbranch_name > > > And I hope, doing just "cvs co module" gives me the latest revision > > on the "main trunk". > > 'cvs co' does a new checkout and is passed full modules on the command line. > > 'cvs up' does an update of the current branch and you pass local > directories or filenames on the command line to be selective about your > update. > > Enjoy! > -- Mark > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.3 (FreeBSD) > > iD8DBQFBf4HJ3x41pRYZE/gRAqdbAKCP/fy94nzotjJaYuBlNkVQpPZyJQCgmngR > RHD/VFlozBjvli5TOHMzKrc= > =wTYb > -----END PGP SIGNATURE----- > _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
