From: Raymond T. <to...@rt...> - 2000-01-24 18:17:42
|
Would it be possible to send the cvs commit messages to another list, say clisp-commit or something? Also can the subjects for these messages be something better than "Changes to /"? CMUCL sends the commit messages to cmucl-commit and the subject line contains the actual file changed by the commit. Just a quick request. Helps me organize my mail a bit better, and I don't have to read every commit to see if it has any immediate implications for me. Thanks, Ray |
From: Sam S. <sd...@gn...> - 2000-01-24 21:46:56
|
>>>> In message <144...@rt...> >>>> On the subject of "[clisp-devel] CVS commit messages?" >>>> Sent on Mon Jan 24 13:24:36 EST 2000 >>>> Honorable Raymond Toy <to...@rt...> writes: >> Would it be possible to send the cvs commit messages to another list, >> say clisp-commit or something? yes, it is possible. do people really WANT it? IMO, the only reason to split commits in a separate group is is there are people who subscribe to clisp-devel but not to clisp-cvs or vice versa. I doubt anyone would. clisp-devel doesn't get too much traffic anyway, and the commits don't happen too often. I read all clisp- and clocc- related lists in the same gnus mail group, and I have no problems. >> Also can the subjects for these messages be something better than >> "Changes to /"? this pisses me off too. I'll look at what can be done. -- Sam Steingold (http://www.podval.org/~sds) Micros**t is not the answer. Micros**t is a question, and the answer is Linux, (http://www.linux.org) the choice of the GNU (http://www.gnu.org) generation. MS DOS: Keyboard not found. Press F1 to continue. |
From: Raymond T. <to...@rt...> - 2000-01-24 21:54:35
|
>>>>> "Sam" == Sam Steingold <sd...@gn...> writes: >>> Would it be possible to send the cvs commit messages to another list, >>> say clisp-commit or something? Sam> are people who subscribe to clisp-devel but not to clisp-cvs Sam> or vice versa. I doubt anyone would. I'm not subscribed to clisp-cvs. Perhaps I should be. Sam> clisp-devel doesn't get too much traffic anyway, and the Sam> commits don't happen too often. I read all clisp- and clocc- Sam> related lists in the same gnus mail group, and I have no Sam> problems. It's not the volume and it's not a problem when I read it. It can be a problem when I want to find something later on. But, it's not a big deal to me, especially if the subject line can be arranged better. >>> Also can the subjects for these messages be something better than >>> "Changes to /"? Sam> this pisses me off too. Sam> I'll look at what can be done. Great! Thanks, Ray |
From: Sam S. <sd...@gn...> - 2000-01-24 23:07:03
|
>>>> In message <144...@rt...> >>>> On the subject of "Re: [clisp-devel] CVS commit messages?" >>>> Sent on Mon Jan 24 17:01:25 EST 2000 >>>> Honorable Raymond Toy <to...@rt...> writes: >> >>>>> "Sam" == Sam Steingold <sd...@gn...> writes: >> >> >>> Would it be possible to send the cvs commit messages to another list, >> >>> say clisp-commit or something? >> >> Sam> are people who subscribe to clisp-devel but not to clisp-cvs >> Sam> or vice versa. I doubt anyone would. >> >> I'm not subscribed to clisp-cvs. Perhaps I should be. it doesn't exist now, but did before the autumn meltdown. so, people, is anyone here going to be subscribed to only one list? unless you speak up, I will keep the current setup. -- Sam Steingold (http://www.podval.org/~sds) Micros**t is not the answer. Micros**t is a question, and the answer is Linux, (http://www.linux.org) the choice of the GNU (http://www.gnu.org) generation. If You Want Breakfast In Bed, Sleep In the Kitchen. |
From: Raymond T. <to...@rt...> - 2000-01-24 23:14:22
|
>>>>> "Sam" == Sam Steingold <sd...@gn...> writes: Sam> so, people, is anyone here going to be subscribed to only one list? Sam> unless you speak up, I will keep the current setup. It doesn't make a big difference to me. But I'd appreciate if you could make the commit messages stand out better. Say include "CVS commit" as part of the subject, or something like that. I'd be happy with that, since I can get procmail to send it off where I want it to go. Thanks for all of your work! Ray P.S. I hate the [clisp-devel] in the subject line but perhaps that how sourceforge works. I find it redundant because I already know what list it's coming from. |
From: Bruno H. <ha...@il...> - 2000-01-25 12:32:46
|
Raymond writes: > It doesn't make a big difference to me. But I'd appreciate if you > could make the commit messages stand out better. Say include "CVS > commit" as part of the subject, or something like that. Mentioning the directory in the subject would be nice too. You have it in the body: "Update of /cvsroot/clisp/clisp/src" It would be nice to have it in the subject too: "[clisp-cvs] commit in /clisp/src" > P.S. I hate the [clisp-devel] in the subject line but perhaps that > how sourceforge works. I find it redundant because I already know > what list it's coming from. I like the [clisp-devel] prefix in the subject. It makes my daily mail screening easier, because I also get [om] and [li18nux] and others. (I don't use procmail - mail is handled on an extra machine here.) Bruno |
From: Eric M. <ema...@ma...> - 2000-01-25 08:19:44
|
>>>>> "Sam" == Sam Steingold <sd...@gn...> writes: Sam> so, people, is anyone here going to be subscribed to only one Sam> list? unless you speak up, I will keep the current setup. I would personally like to have a separate list for cvs commits (since I probably won't be subscribed to it). I also vote for no silly [subj] insertion. FWIW. -- Eric Marsden |
From: Sam S. <sd...@gn...> - 2000-01-24 23:24:48
|
>>>> In message <144...@rt...> >>>> On the subject of "Re: [clisp-devel] CVS commit messages?" >>>> Sent on Mon Jan 24 18:21:13 EST 2000 >>>> Honorable Raymond Toy <to...@rt...> writes: >> >> P.S. I hate the [clisp-devel] in the subject line but perhaps that >> how sourceforge works. I find it redundant because I already know >> what list it's coming from. I can change that. do you want it to be gone? replaced with [CD]? [cd]? [clisp]? make your choice. (others please participate in this important discussion! :-) -- Sam Steingold (http://www.podval.org/~sds) Micros**t is not the answer. Micros**t is a question, and the answer is Linux, (http://www.linux.org) the choice of the GNU (http://www.gnu.org) generation. Binaries die but source code lives forever. |
From: Raymond T. <to...@rt...> - 2000-01-24 23:31:45
|
>>>>> "Sam" == Sam Steingold <sd...@gn...> writes: Sam> I can change that. Sam> do you want it to be gone? Sam> replaced with [CD]? [cd]? [clisp]? Sam> make your choice. Sam> (others please participate in this important discussion! :-) My vote: make it go away. (Same goes for the clisp-list list too. :-) ) Second vote: Leave it as it is (I don't like the other choices you've made---too brief, and [clisp] is too confusing with [clisp-list].) Thanks, Ray |
From: Paolo A. <am...@mc...> - 2000-01-25 13:50:57
|
On 24 Jan 2000 18:23:54 -0500, you wrote: > do you want it to be gone? > replaced with [CD]? [cd]? [clisp]? > make your choice. I think that the tag can be dropped completely. All email applications worth of this name can automatically file messages to different folders based on the contents of header fields. If I have a clisp-devel folder, it's redundant to have an additional [something] tag which, by the way, reduces the precious space available for the subject field. Paolo -- EncyCMUCLopedia * Extensive collection of CMU Common Lisp documentation http://cvs2.cons.org:8000/cmucl/doc/EncyCMUCLopedia/ |
From: Randall R S. <rrs...@cr...> - 2000-01-25 16:26:53
|
Sam, My votes: - Get rid of the [list-name] -- It wastes valuable space for meaningful subject content (and, I dare say it, most programmers have no experience in headline writing) - The CVS messages are OK, but getting the name of the file modified would be very desirable. - No need to split the list. As was pointed out by another responder, decent mail filtering can recognize the fixed portion of a CVS commit message Subject: heading, assuming it's sufficiently distinct from anything likely to appear in a manual posting. Randy Schulz Mountain View, CA USA At 18:23 -0500 1/24/00, Sam Steingold wrote: >... >(others please participate in this important discussion! :-) > >Sam Steingold |