Re: gettext->gnulib sync conflicts

[Karl Berry]

    However, in periods where only small and safe changes are being made,

The problem from my point of view is that I just see a change and can't
(don't want to) guess if it's "small and safe". If I can't blindly sync
the changes I see, that creates an additional burden that I can't (don't
want to) support.

This is not the first time this has come up wrt your gettext changes in
gnulib. (It's never come up wrt anything else.) The last time it
happened, the outcome we agreed on was to stop syncing gettext with
gnulib entirely, and you would do it manually, as you saw fit.

Then stopped having time to work on stuff for a while, and after
discussing with Daiki, I went back to the sync-with-releases regime,
since (not surprisingly) files had gotten out of sync -- the manual
sync by the maintainer is an easy thing to neglect.

I can sync against dev, or I can sync against releases, or I can not
sync at all, or I can quit being responsible for this job entirely and
someone else can figure out what to do :). I can't go back and forth
depending on development "periods". [Or gettext could be removed from
gnulib entirely, which I tend to think would tremendously simplify
everything for everyone, but doubt you like the idea.]

Sigh.

    Daiki needs to decide.

Daiki?  --thanks, karl.