[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#8675: lisp_string_width and strings wider than INT_MAX
From: |
Eli Zaretskii |
Subject: |
bug#8675: lisp_string_width and strings wider than INT_MAX |
Date: |
Mon, 16 May 2011 10:57:34 +0300 |
> Date: Sun, 15 May 2011 22:33:03 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: 8675@debbugs.gnu.org
>
> On 05/15/11 22:30, Eli Zaretskii wrote:
> >> Date: Sun, 15 May 2011 22:07:36 -0700
> >> From: Paul Eggert <eggert@cs.ucla.edu>
> >>
> >> PATCH 3 depends on two obvious patches: PATCH 2 introduces a helper
> >> no-return function string_overflow, and PATCH 1 updates to the latest
> >> version of gnulib.
> >
> > Thanks, but why do these patches come with unrelated changes in
> > texinfo.tex?
>
> Because that's part of PATCH 1, which updates to the latest version
> of gnulib. Gnulib contains texinfo.tex. PATCH 1 was generated
> entirely automatically by "make sync-from-gnulib".
When you merge, could you please make the texinfo.tex update a
separate commit on the trunk, then? No one will ever expect to find
that file in a commit logged as "sync from gnulib", which will make
forensics more difficult than it needs to (since your commits are
always merge-commits).
TIA
bug#8675: committed fix into trunk, Paul Eggert, 2011/05/17
- bug#8675: committed fix into trunk, Christoph Scholtes, 2011/05/17
- bug#8675: committed fix into trunk, Paul Eggert, 2011/05/17
- bug#8675: committed fix into trunk, Christoph Scholtes, 2011/05/17
- bug#8675: committed fix into trunk, Andreas Schwab, 2011/05/18
- bug#8675: error: token "@" is not valid in preprocessor expressions, Paul Eggert, 2011/05/18
- bug#8675: error: token "@" is not valid in preprocessor expressions, Andreas Schwab, 2011/05/18