[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gettext->gnulib sync conflicts
From: |
Daiki Ueno |
Subject: |
Re: gettext->gnulib sync conflicts |
Date: |
Mon, 21 Nov 2016 10:50:57 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) |
Hello,
Karl Berry <address@hidden> writes:
> 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.
I'm not really sure what I need to decide. Is there any room for
compromise between the sync-with-releases mechanism and manual
check-ins? I thought it would be possible to avoid unwanted overwrites
if srclist-update were aware of the serial numbers of the files.
Regards,
--
Daiki Ueno
- gettext->gnulib sync conflicts, Karl Berry, 2016/11/18
- Re: gettext->gnulib sync conflicts, Bruno Haible, 2016/11/18
- Re: gettext->gnulib sync conflicts, Karl Berry, 2016/11/20
- Re: gettext->gnulib sync conflicts,
Daiki Ueno <=
- Re: gettext->gnulib sync conflicts, Karl Berry, 2016/11/21
- Re: gettext->gnulib sync conflicts, Daiki Ueno, 2016/11/22
- Re: gettext->gnulib sync conflicts, Paul Eggert, 2016/11/22
- Re: gettext->gnulib sync conflicts, Daiki Ueno, 2016/11/22
- Re: gettext->gnulib sync conflicts, Daiki Ueno, 2016/11/23
- Re: gettext->gnulib sync conflicts, Karl Berry, 2016/11/23
- Re: gettext->gnulib sync conflicts, Karl Berry, 2016/11/22