Feature suggestion

Hi developers,

Thank you all for trying to replace cvs, it's about time!

One feature that I think cvs is missing and that I don't think I've seen
requested other places is this: Built in support for ChangeLog files. The
most annoying part of running cvs on bigger projects (like gcc, glibc etc) is
that ChangeLogs needs to be handled manually for each commit.

The problem is this: As development goes on for a new gcc patch, ChangeLog
entries are written. Now, if the developer wants to update the tree, he has
to remove his ChangeLog entries, do the update and reinsert them. This
usually happens multiple times during patch development. Then, when the cvs
diff is to be sent to the mailing list, again the ChangeLog entries has to be
removed, since it's bad form to send ChangeLog patches. And finally when you
commit, the entries can be put there for good.

There are basically two different ways to deal with it: Write ChangeLogs in a
separate file and keep it there until committing or simply write the
ChangeLog entries directly in the email when the patch is sent to the list.
Developers usually take the second approach, resulting in less than optimal
ChangeLogs.

Right now, it's too awkward to handle ChangeLogs and it's something many
developers waste time on. It's the obvious requirements for an automated
solution: Manual, repetitive, boring and easily handled by an application.
It's one of those seemingly silly problems that is surprisingly painful in
the long run. It has annoyed me to the point where I was about to look at cvs
sources and just do it myself.

I hope you will consider doing this.

Bo.

-- 
     Bo Thorsen                 |   Praestevejen 4
     Free software developer    |   5290 Marslev
     SuSE Labs                  |   Denmark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org