Just FYI -
I did this kind of stuff over the summer - I really pimped-out CVS. We made
it check for binary files, remove line endings, and send out commit mails,
etc... The way I did it, we only go one message for each set of commits -
unlike how Bonsai now displays our commit data, so this behavior is totally
possible to achieve.
Is it desirable? Well, a lot of times I notice that people (myself included)
like to post additional information to the list that they didn't include in
their commit message (e.g. a link to screen-shots or a functional
description). I'm up in the air as to whether I'm in favor of this or not,
so I'll let others decide :)
Dom
>From: "Mike Nordell" <[EMAIL PROTECTED]>
>To: "AbiWord-dev" <[EMAIL PROTECTED]>
>Subject: Re: REQ: Commit in subj.
>Date: Sun, 28 Jan 2001 08:37:58 +0100
>
>Aaron Lehmann wrote:
> > On Sun, Jan 28, 2001 at 08:19:13AM +0100, Mike Nordell wrote:
> > > However convenient that would be it could be a disaster when
>committing
> > > files in seven different directories for one patch. Seven mails?!
>Don't
> > > think so. :-)
> >
> > Not really.
> >
> > cvs commit foo bar baz fred barney # ...
>
>I don't know if you agree with me here or if yu display a way to only get
>one mail for seven commits. If it's the latter I must inform you that any
>GUI CVS client would probably only allow you to co�mmit from one directory
>at a time (i.e. WinCvs). Yes, it sucks when working as we do, but its the
>paradigm at least I have to live with for now (yes, I know I can use the
>command-line version but I haven't got a clue how that one handles the path
>differences).
>
>/Mike - just don't. Please.
>
>
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
