zsh-workers
 help / color / mirror / code / Atom feed
From: mason@primenet.com.au (Geoff Wing)
To: zsh-workers@sunsite.auc.dk
Subject: Re: sourceforge.net CVS tree ready for use
Date: 2 Apr 2000 06:02:08 GMT	[thread overview]
Message-ID: <slrn8edoj0.ft8.mason@coral.primenet.com.au> (raw)
In-Reply-To: <1000402043752.ZM17756@candle.brasslantern.com>

Bart Schaefer <schaefer@candle.brasslantern.com> typed:
:On Apr 2,  1:45am, Adam Spiers wrote:
:} Subject: Re: sourceforge.net CVS tree ready for use
:} We set up automatic e-mail notification of any commits.  (This
:} would be easy enough[0].)
:I'm curious whether you've found a way to prevent the generation of
:one message per subdirectory when a commit spans several subdirs.
:CVS is rather insistent that every directory is a "module" ... and
:given that there are 8 subdirectories under Completion alone, we
:certainly don't want one mesage per directory per commit fired off
:to zsh-workers (or even to some new zsh-cvs-commits list).

Yes, I was about to request this.  Aggregation of commit messages which
occur at the same time, plus or minus a few seconds (to account for
directory spanning when people might use ! to CVS to reuse a log message),
and with the same log info would be very nice.  Somewhere I've got a perl
program to insert into CVSROOT/loginfo, though it depends on what we can
run on their server.  Otherwise some external aggregator should/could be
set up.

Regards,
-- 
Geoff Wing : <gcw@pobox.com>     Work URL: http://www.primenet.com.au/
Rxvt Stuff : <gcw@rxvt.org>      Ego URL : http://pobox.com/~gcw/
Zsh Stuff  : <gcw@zsh.org>       Phone   : (Australia) 0413 431 874


  reply	other threads:[~2000-04-02  6:02 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-26  0:50 zsh license preventing move to sourceforge.net? (fwd) Adam Spiers
2000-03-26 19:06 ` Clint Adams
2000-03-26 22:19 ` Peter Stephenson
2000-03-28  0:28   ` move to sourceforge.net in progress Adam Spiers
2000-03-27 21:24     ` Peter Stephenson
2000-04-01 11:11       ` sourceforge.net CVS tree ready for use Adam Spiers
2000-04-01 20:51         ` Peter Stephenson
2000-04-02  0:44           ` Bart Schaefer
2000-04-02  0:45           ` Adam Spiers
2000-04-02  4:37             ` Bart Schaefer
2000-04-02  6:02               ` Geoff Wing [this message]
2000-04-02 22:02                 ` Adam Spiers
2000-04-02 23:16                   ` Bart Schaefer
2000-04-02 10:10         ` Andrej Borsenkow
2000-04-02 10:35           ` Geoff Wing
2000-04-02 23:29             ` Bart Schaefer
2000-04-03  8:50               ` Geoff Wing
2000-04-03 10:30         ` Oliver Kiddle
2000-04-03 13:06           ` Adam Spiers
2000-03-28  1:46     ` move to sourceforge.net in progress Bart Schaefer
2000-03-28 11:45     ` Andrej Borsenkow
2000-03-28 16:51       ` Bart Schaefer
2000-04-02 14:06 sourceforge.net CVS tree ready for use dmeyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=slrn8edoj0.ft8.mason@coral.primenet.com.au \
    --to=mason@primenet.com.au \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).