Re: Distfiles

[Jim Meyering]

On Thu, Sep 10, 2020 at 9:50 AM Jim Meyering <jim@meyering.net> wrote:
>
> On Wed, Sep 9, 2020 at 8:50 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
> >
> > On 9/8/20 10:04 AM, Issam E. Maghni wrote:
> >
> > > Could you please offer .tar.gz ditfiles on upcoming releases? It’s 
> > > already the
> > > case for GNU Coreutils, starting from version 8.32, and GNU sed, starting 
> > > from
> > > version 4.8 thanks to the push from Guix team [1].
> > >
> > > [1] 
> > > https://guix.gnu.org/blog/2020/guix-further-reduces-bootstrap-seed-to-25/
> >
> > That sounds like the right thing to do, so I installed the attached patches 
> > (the
> > first one just documents the need for xz support).
>
> Thanks for all your recent patches!
>
> > I also tagged the v3.4 commit; somehow that tag wasn't pushed into Savannah 
> > when
> > 3.4 came out.
>
> Tagging is a hard-to-avoid part of the release process, and it did
> indeed tag a commit with v3.4:
> 7aa77dd6ea378c1e528e276761617b7dab411d2e, and it was pushed (per an
> auto-generated email I received), but there was a minor snafu: you
> were pushing a change precisely while I was making that release, and

Note that while I pushed the tag, I never pushed that dangling commit,
7aa77dd6ea378c1e528e276761617b7dab411d2e. It is identical to
d1aaacee20667a95b11d23ef38764aca4772d8cc, but would have resided in
the tree where your commit landed.