I would like to vote for this feature too. CVS's support for bug
tracking is poor to nonexistent and many people have commented on
it and requested better support. Tags don't really do it.

Steve Buroff

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
Terrence Enger
Sent: Monday, December 09, 2002 11:19 AM
To: Andrew Johnson; [EMAIL PROTECTED]
Subject: Re: Bug tracking.


At 14:37 2002-10-11 -0500, Andrew Johnson wrote:
>J wrote:
>>
>> Yes, but what I would like is a uniqe commit number, whatever it
may be,
578
>> for instance applied to all the files involved in that single
commit.
>
>That's just not how CVS works, and it never will.

Could you please tell us why think cvs will never have this feature?
If
you think it should never have this feature, I would like to hear
about
that, too.

The feature would allow automatic recovery of some of the information
which
developers--including the developers of cvs itself--maintain manually
in
the files Changelog, so I do not see how it could be a *bad* thing to
offer.

>
>However I believe Subversion uses this approach, go have a look at
that.
>If you're not willing to change the way you think/work to match the
tool,
>you'll have to change the tool instead.
>
>- Andrew
>--
>"Life is what happens while you're busy making other plans." - John
Lennon
>
>_______________________________________________
>Info-cvs mailing list
>[EMAIL PROTECTED]
>http://mail.gnu.org/mailman/listinfo/info-cvs
>_______________________________________________
>Info-cvs mailing list
>[EMAIL PROTECTED]
>http://mail.gnu.org/mailman/listinfo/info-cvs
>
>



_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs



_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Reply via email to