Re: Not clear what is going on with site and git.

On 5/29/26 23:06, Peter Korsgaard wrote:
>>>>>> "Harald" == Harald van Dijk <[email protected]> writes:
> 
> Hi,
> 
>   > At any rate, if the request gets missed and people need to refer back
>   > to it later, 1.38.0 is identical to current git master, commit
>   > ead17e7808236be80614d0a8755f4ddad63ab56c.
> 
> Ehh, current git master is 244c0a01eece537e9d7e8318a5c320a836cc604b
> (testing stripts: allow to skip "awk gsub erroneous word start match"
> test) and looking in the Makefile in busybox-1.38.0.tar.bz2 I would
> think that the corresponding git commit is
> fc71374dfccd46448c62947269a35f1420d7ee28 (Bump version to 1.38.0), E.G.
> 1 commit after ead17e7808236be80614d0a8755f4ddad63ab56c.

Right, that commit just applies part 1 of the release making process to 
ead17e7808236be80614d0a8755f4ddad63ab56c, clearing EXTRAVERSION. But 
thanks, I'm not sure why I hadn't seen that commit (or later commits) yet.

> I do see that the tarball is identical to
> fc71374dfccd46448c62947269a35f1420d7ee28 except that the tarball does
> not include the .gitignore files:

That part is done by the scripts/bb_release script, again the normal 
release making process: the .gitignore files in the repository are meant 
to be kept out of the release tarball. It's been that way for previous 
releases too.

Cheers,
Harald van Dijk