On 9/10/20 1:26 AM, Jim Meyering wrote:
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.
Hmm, I'd forgotten about that snafu. So should I remove the "v3.4" tag?
It doesn't actually correspond to grep 3.4.
Another possibility is that you start a short branch, one containing
only the dangling commit 7aa77dd6ea378c1e528e276761617b7dab411d2e and
its ancestors. Presumably it would look like this, tip first:
7aa77dd6ea378c1e528e276761617b7dab411d2e version 3.4
???????????????????????????????????????? build: update gnulib to latest,
for mbrtowc-vs-Irix build fix (this is the dangling-commit analog to
a9d19cf2fecf925928499b59ff41da1e03cc4e4e)
767c83fd302f05a8b790a78eacce11aac50903ee doc: fix --exclude description
in man page (this is also in the master branch)
and we then tag 7aa77dd6ea378c1e528e276761617b7dab411d2e as v3.4.
Yet another possibility is to rename the "v3.4" tag to "almost3.4", or
"v3.4-almost", or something like that.