[shell-coding] Re: cvs
- From: "Shaheen Gandhi" <sgandhi@xxxxxxxxxxxxxx>
- To: <shell-coding@xxxxxxxxxxxxx>
- Date: Thu, 11 Jul 2002 20:07:58 -0700
Perforce is a frickin' awesome sccs. Their free-for-use license is a
bit strange, but you might be able to use it for free.
And yes, it requires a log message for each checkin.
- Visigoth
> -----Original Message-----
> From: shell-coding-bounce@xxxxxxxxxxxxx
> [mailto:shell-coding-bounce@xxxxxxxxxxxxx] On Behalf Of
> Bgvinyard@xxxxxxx
> Sent: Thursday, July 11, 2002 1:54 PM
> To: shell-coding@xxxxxxxxxxxxx
> Subject: [shell-coding] cvs
>
>
> I know most of us use cvs in one form or another to manage
> our source trees,
> one thing that drives me absolutely crazy is commits without
> a log message. I
> was looking into a way to prevent this and came across the following:
>
http://www.mail-archive.com/info-cvs@xxxxxxx/msg11237.html
With this as a reference:
http://www-es.fernuni-hagen.de/cgi-bin/info2html?(cvs)verifymsg
Now I don't have the slightest clue when it comes to writing shell
scripts or
anything of the sort, but perhaps if someone on this list does, it might
benefit us all... would be one step closer to getting the change log
automagically generated from the commit log messages, and one less thing
for
the developers to have to maintain.
Thanks,
Bobby G. Vinyard
__________________________________________________
Subscription options and archive:
http://www.freelists.org/list/shell-coding
__________________________________________________
Subscription options and archive:
http://www.freelists.org/list/shell-coding
- References:
- [shell-coding] cvs
- From: Bgvinyard
Other related posts:
- » [shell-coding] cvs
- » [shell-coding] Re: cvs
- » [shell-coding] Re: cvs
- » [shell-coding] Re: cvs
- » [shell-coding] Re: cvs
- » [shell-coding] Re: cvs
- [shell-coding] cvs
- From: Bgvinyard