bug-cvs
[Top][All Lists]
Advanced

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

Re: CVS log


From: Mark D. Baushke
Subject: Re: CVS log
Date: Sat, 02 Oct 2004 16:50:08 -0700

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

Richard <address@hidden> writes:

> This is not really a bug report, but a suggestion. When doing a "cvs log 
> somefile", print the file versions chronologically on the screen like 
> 
> ----------------------------
> revision 1.1
> date: 2004/06/09 15:50:02;  author: gg;  state: Exp;
> new file
> ----------------------------
> revision 1.2
> date: 2004/06/16 20:10:50;  author: xy;  state: Exp;  lines: +1 -1
> another log
> ----------------------------
> revision 1.3
> date: 2004/06/22 11:37:39;  author: xx;  state: Exp;  lines: +1 -1
> Some log message
> =============================================================================
> 
> and not
> 
> ----------------------------
> revision 1.3
> date: 2004/06/22 11:37:39;  author: xx;  state: Exp;  lines: +1 -1
> Some log message
> ----------------------------
> revision 1.2
> date: 2004/06/16 20:10:50;  author: xy;  state: Exp;  lines: +1 -1
> another log
> ----------------------------
> revision 1.1
> date: 2004/06/09 15:50:02;  author: gg;  state: Exp;
> new file
> =============================================================================
> 
> Usually, we need the latest log more than the first one.

I disagree. The current reverse chronological order by branch makes more
sense to me.

If I am working in a checked out tree and do an update and
something no longer works, I usually wish to locate the most recent
changes that may have conspired to give me trouble. A file with only
three versions is not a big deal one way or another. However, when the
number of versions is more than a few thousand, you really do want the
current implementation to be used with ancient history coming last.

Consider doing a cvs log of ccvs/src/ChangeLog which has more than 2900
revisions on the mainline and just under 80 revisions on the stable
branch.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)

iD8DBQFBXz6w3x41pRYZE/gRAqnfAKCVeYj/Zykk+7xpjgQSPnioHSQvrgCeK0A5
larKtEZDu4uIicz/xlutZtU=
=a5Gv
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]