Re: Convert mailnotify headers to git.

[Gary V. Vaughan]

On 7 Sep 2008, at 04:02, Ralf Wildenhues wrote:
> * Eric Blake wrote on Sat, Sep 06, 2008 at 09:56:29PM CEST:
> > According to Gary V. Vaughan on 9/6/2008 1:51 PM:
> > > Root:           /srv/git/libtool.git
> > > Timestamp:      1.3012 2008-09-07
> > > Branch:         master
> > > Changes by:     address@hidden
> > >
> > > Log Message:
> > >         Convert mailnotify headers to git.
> > >         * clcommit.m4sh: Improve mailnotify contents.
> >
> > But no patch to go along with the log message?  And is mailnotify  
> > still
> > necessary, now that savannah can automatically send mail about  
> > commits?
>
> A message to libtool-commit is generated automatically.
> A generated message to libtool-patches seems superfluous.
> If there is some additional comments to make, then a manual
> message to libtool-patches is useful.  If there are no
> additional comments, should there be an optional stub message
> like the above, or none at all, or should we always write
> manual messages?

I'm just converting the former cvs machinery to git at the moment,
so that the HACKING release notes are coherent again.

Ultimately, this stuff is supposed to send either an FYI with
a patch attachment, or an 'okay to commit?' message.

Although the half cocked messages the current script posted are
not useful (other than to show the converted libtool commit
scripts are working) I'm don't have any strong feelings about
what the posting policy ends up being.  However, I would like
to push the 'okay to commit?' posting code I have into libtool
for everyone elses benefit after the release...

> Just thinking out loud, babbling,
> Ralf

Me too :)

Cheers,
    Gary
--
Email me:          address@hidden                          ._(()
Read my blog:      http://blog.azazil.net                 \' )
And my other blog: http://www.machaxor.net                =( \
...and my book:    http://sources.redhat.com/autobook     _(~_)'