[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] [Mint-cvs] [FreeMiNT CVS] freemint/xaaes/src.km

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2011-01-08 15:00, Helmut Karlowski wrote:
> Why does cvs offer commit -r then at all?

I would refer to it as an expert option.  It is as simple as "Unless you
know how to use it, don' t use it."  and I found that i causes more
waste of my time than it is useful.  What I described works always and
is the widely accepted work flow.  It guarantees avoiding situations
like the one you found yourself in.  Here is an excerpt from the CVS
info page about the commit command:

[...]

 `commit' verifies that the selected files are up to date with the
current revisions in the source repository; it will notify you, and
exit without committing, if any of the specified files must be made
current first with `update' (*note update::).  `commit' does not call
the `update' command for you, but rather leaves that for you to do when
the time is right.

[...]

`-r REVISION'
     Commit to REVISION.  REVISION must be either a branch, or a
     revision on the main trunk that is higher than any existing
     revision number (*note Assigning revisions::).  You cannot commit
     to a specific revision on a branch.

Cheers,
	T.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0o4R0ACgkQMiyRSD9s+zVjRQCeIm0PvHls5u5vZlp0C57yZBk7
BgEAn0CsofnrZmbqxm0wx9sBnDi3h63z
=9flM
-----END PGP SIGNATURE-----