Re: Preparing hypermail cvs commit/merge, suggestions?

From: Daniel Stenberg <>
Date: Sun, 5 Sep 1999 18:44:57 +0200 (MET DST)
Message-ID: <>

On Fri, 3 Sep 1999 wrote:

> BTW, I'm not sure on how to update the man files (.4). Just edit them and
> add the new options?

Yes please! ;-) The man pages are lagging behind terribly.

> How would you like me to proceed to make this merge commit? I see two
> options:
> - Someone volunteers (Paul?) to run my hypermail on some of his files and
> see if he has the same result. If it's ok, I'll commit my changes then
> - I commit my changes to the base and fix any bugs that may appear from them
> as they are reported.

I think you should do this:

  1. Tag the current sources with some intelligent name and then
  2. Commit all your changes.

This lets all of us that use the CVS server to try your fixes and when we think they work out we can release a tarball. If any CVS-user finds the newly commited major revision to be a bad thing, (s)he can easily revert back to the revision just before thanks to the tags.

> I don't know how many parallel hypermail developments are taking place
> right now

I don't think there's any. AFAIK, we're only four people that have write permissions and I am not doing anything at the moment, Paul has said before that he has limited time for this now and Ashley only has a configure change.

That's all I know.

> Following a known developer's rule, I won't make this commit before
> Monday and before receiving a go-ahead from the other developers/users.

I say go ahead, let's face the problems when they come.

Very good job and I want to take this opportunity to welcome you aboard the hypermail development joyride! ;-)

  Daniel Stenberg
  Get in the latest development versions of hypermail from:
Received on Sun 05 Sep 1999 06:44:29 PM GMT

This archive was generated by hypermail 2.3.0 : Sat 13 Mar 2010 03:46:11 AM GMT GMT