Re: [Nmh-workers] Announcing the release of nmh-1.7

[Ralph Corderoy]

Hi Ken,

> I am pleased to announce the long-awaited release of nmh 1.7!

Well done.  That's me switching back to running git now the other guinea
pigs have arrived.  :-)

I was looking at git's tags, and how the convention has changed over
time.

    $ for t in `git tag`; do
    >     printf '%6d  %s\n' `git rev-list --count $t` $t
    > done |
    > LC_ALL=C sort -k1,1n -k2 |
    > pr -t2 | expand
       200  nmh-1_0                       1107  1.5-branchpoint
       201  nmh-1_0_2                     1108  1.5-RC1
       202  nmh-1_0_3                     1125  1.5-RC2
       203  nmh-1_0_4                     1141  1.5-RC3
       253  kim-before-sasl               1150  1.5
       504  RELEASE_1_2                   2384  1.6-branchpoint
       588  nmh-1_3_RC1                   2386  1.6-RC1
       596  nmh-1_3_RC2                   2395  1.6-RC2
       603  nmh-1_3_RC3                   2425  1.6-RC3
       604  nmh-1_3                       2430  1.6
       664  PRE_POSIX_CONVERSION          3855  1.7-branchpoint
       670  cvs-repository-moved-to-git   3857  1.7-RC1
       700  nmh-1_4_RC1                   3868  1.7-RC2
       702  nmh-1_4_RC2                   3889  1.7-RC3
       703  nmh-1_4                       3897  1.7
    $

Can we add, say, annotated tag `1.4' to the same commit as nmh-1_4, and
likewise for 1.{2,3} releases?  It would make it easier to script using
releases, and save having to remember the format when typing.  Maybe
there's a git reason not to do this.

The `To' header on the email I received was interesting.

    To: nmh-announce: ;, ""@ruis.pair.com, address@hidden

ruis.pair.com is one of the final hops before reaching me, suggesting
they've added the domain.

I looked for a decent online mail archive that gives access to the
"original" and found
https://www.mhonarc.org/archive/cgi-bin/extract-mesg.cgi?a=nmh-workers&m=2017-11&i=20171119004244.DA4E6A19F9%40pb-smtp2.pobox.com

    To: nmh-announce: ;@zimbra.mallorn.com, address@hidden

So different, but still weird different.  Again, mallorn.com is near the
end of the route.  This time, no comma with `""' for the username of a
second address.

What did you write?  I'm guessing the perfectly valid `nmh-announce: ;'?

-- 
Cheers, Ralph.
https://plus.google.com/+RalphCorderoy