Hello Bruno, Bruno Haible <br...@clisp.org> writes:
> On 2019-03-03 I listed the problems that I have with the existing practices > of using gnulib as a submodule. > > Here's my attempt to fix this for the packages I maintain (gettext, > libunistring, etc.). It's a new script 'gitsub.sh'. I should have commented earlier, but I wanted to express my motivation behind the switch to using "git submodule" in gettext. That was not for making upgrades easier, but for making change tracking easier. Prior to the switch, I could only see the "Update after gnulib changed." messages in the "git log" output, without any mention of the target revisions of gnulib. That was making "git bisect" hard. With "git submodule", those gnulib revisions are automatically recorded and I can easily move back to a specific revision of the gettext, which is somehow guaranteed to compile. Therefore, if the new script provides a similar feature, without adding a manual process to our current practice, I wouldn't oppose. Otherwise it seems like a bit of a step back to me. Regards, -- Daiki Ueno
