On Thu, Feb 12, 2026 at 11:56:24AM +0800, Otto Kekäläinen wrote:
all the additions found in the tarball are generated automatically I
assume. Why can't they be simply added to the Git repo while creating
the tag in a classic "Releasing version foo" commit? (A common pattern
Isn't the obvious solution to use dual git+tarball imports?
If that's a well-known term, then I still don't know it. Can you point
me to some insight?
To the previous poster, my idea would be:
- decide to publish HEAD
- tag with a pre-release tag like pre/v1.2.3
- branch off pre/v1.2.3
- do the pre-relase changes (version number, contributor list,
autoreconf etc bla)
- tag v1.2.3, sign that
- optionally: publish tarball
- continue development from the original branch, leaving the release
branch behind (maybe backporting fixes etc for maintenance releases
from there)
But surely that's wrong in some way.
However, is there are any special stuff going on in the
tarball due to upstream practices, that will show up in the import
commit
That would be the famous-and-feared case of a merge commit that ALSO
comes with its own diff (those are my ultimate adversary), right?
Greetings
Marc
--
-----------------------------------------------------------------------------
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
