Re: [jamboost] Re: Commit emails

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-05-03 10:19:55

----- Original Message -----
From: "Vladimir Prus" <ghost_at_[hidden]>
To: <jamboost_at_[hidden]>
Sent: Friday, May 03, 2002 9:32 AM
Subject: Re: [jamboost] Re: Commit emails

> David Abrahams wrote:
> > Oh, OK.
> >
> > Well, I'm not yet convinced that this is a good idea for us. Boost
is
> > big and it doesn't seem like there's a way to limit the emails to
> > Boost.Build-related ones. As the page says:
> >
> > " If you have started a successful Open Source project, you will not
be
> > able to catch up with your email. If you can keep up with it and
still
> > have time to hack, you need to make your project more attractive to
> > others, so you can get more developers checking in more changes.
Then
> > you'll always have more email than you know what to do with! "
>
> But, somewhere above, it says:
>
> "If you have several sub-products for which you want different checkin
lists,
> you can change the "DEFAULT" label to match the subtree that you want
to go
> to each list, with a separate line for each distinct prefix. For
example, if
> your project includes the products "one" and "two", you could use the
> following:
> CVSROOT $CVSROOT/CVSROOT/syncmail %{sVv} you_at_someplace.else
>
> one/ $CVSROOT/CVSROOT/syncmail %{sVv}
myproject-one-cvs_at_[hidden]
> two/ $CVSROOT/CVSROOT/syncmail %{sVv}
myproject-two-cvs_at_[hidden]"

Oh!

OK, I just spent a half hour trying to checkin the script (from a Unix
machine, since I have no confidence that +x sticks through cygwin CVS).
If you could do everything that doesn't require admin privileges, I'll
set up the rest.

-Dave