Re: gettext->gnulib sync conflicts

[Daiki Ueno]

Karl Berry <address@hidden> writes:

> Hi Daiki (and all),
>
>     if srclist-update were aware of the serial numbers of the files.
>
> 1) Not all synced files have serial numbers.
>
> 2) It's not clear to me that the decision about syncing
> should, in principle, be based on serial numbers (or timestamps).
>
> 3) Nevertheless I have no particular objection to the idea (it would
> solve the immediate question, I guess), but I also don't feel like
> implementing it. I doubt it's going to be the top of anyone else's
> priority list either. Therefore I've disabled syncing of all
> gettext<->gnulib files in gnulib/config/srclist.txt.
>
> Feel free to revert/change as you like, at any time ... --best, karl.

Sorry, I probably do not understand the problem.  Why can't we continue
syncing with the gettext releases, even if one checks in a change into
gnulib directly?

That would probably work, even without checking the serial numbers,
because gettext has a way to detect conflicts when making a distribution
tarball:
http://git.savannah.gnu.org/cgit/gettext.git/tree/Makefile.am#n62

I barely remember the last discussion, but my motivation was to
eliminate the manual procedure to propagate changes from gettext after
every release.

So, I would like to ask you to continue doing sync-with-releases
(ignoring the changes made in gnulib git repository), unless it is too
much burden for you.

Thank you,
-- 
Daiki Ueno