Re: What is xreadline?

> On Jul 1, 2024, at 12:46 PM, Reuben Thomas wrote: > > readtokens.c has a comment saying "This almost supersedes xreadline stuff", > but I can't find out what xreadline is. > > -- > https://rrt.sc3d.org IIUC it’s the xreadline.c from gnupg. Cheers, Gary

Re: bootstrap/autogen.sh and git submodules

> On Mar 3, 2019, at 10:03 AM, Bruno Haible wrote: > > Hi, > > When gnulib is used in a package, often the maintainers of that package > use it via a git submodule, because that enables them to upgrade to newer > versions of gnulib when they want to (and have a failsafe build between > these u

Re: bootstrap regression ?

> On Mar 2, 2019, at 10:08 AM, Tim Rühsen wrote: > >> On 02.03.19 17:52, Gary V. Vaughan wrote: >> >> On Mar 1, 2019, at 1:42 PM, Tim Rühsen > <mailto:tim.rueh...@gmx.de>> wrote: >> >>> Hi, >>> >>> at GnuTLS we have one g

Re: bootstrap regression ?

> On Mar 1, 2019, at 1:42 PM, Tim Rühsen wrote: > > Hi, > > at GnuTLS we have one git submodule that is not 'active' by default - > this is on purpose since we want to init it just in certain cases. > > The latest 'bootstrap' script doesn't accept this and stops with an error: > "./bootstrap:

Re: Question about build-aux/bootstrap regarding $(...)

> On May 16, 2017, at 8:12 AM, Eric Blake wrote: > >> On 05/16/2017 12:47 AM, Akash Rawal wrote: >> Hello everyone Hi, >> I observed that build-aux/bootstrap uses $(command) for command >> substitution which is known to be less portable than `command`.[1] > > It's less portable only if you st

Re: [PATCH 0/5] obstacks again

your application suddenly use up all the available memory. Which is a shame, because, other than that M4 would have been perfectly functional after the gnulib bump without any special client code changes. If there's a way to at least diagnose negative arguments rather than silently change behavior, that would save other projects some migration headaches... Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: recent changes to obstacks cause many out of memory failures in M4 master testsuite

Hi Eric, > On Dec 5, 2014, at 7:11 PM, Eric Blake wrote: > > On 12/05/2014 12:03 PM, Gary V. Vaughan wrote: > >> Bisecting my way to the the first gnulib changeset that causes these >> failures, I landed at: >> >> bb2ab7e 2014-10-29 14:02 Alan Modra o

recent changes to obstacks cause many out of memory failures in M4 master testsuite

revisions prior to that allow m4 to pass it's tests, but I'm afraid I don't understand the change well enough to point at the actual root of the issue. Hopefully someone here more knowledgable than I will be able to advise. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: EXEEXT for other languages

Hi Reuben, > On Jan 11, 2014, at 9:37 PM, Reuben Thomas wrote: > >> On 11 January 2014 03:49, Gary V. Vaughan wrote: >> Hi Reuben, >> >> On Jan 11, 2014, at 3:12 PM, Reuben Thomas wrote: >> >> > I have a project that installs a C program and a

Re: EXEEXT for other languages

its > use? I would write an install-exec-hook in your Makefile.am that performs any post-install renames according to whatever logic you deem appropriate :) http://www.gnu.org/software/automake/manual/automake.html#Extending Cheers, -- Gary V. Vaughan (gary AT gnu DOT org) signatur

Re: as_echo/bs_echo still required?

Hi Paul, On Jan 2, 2014, at 3:45 PM, Paul Eggert wrote: > Gary V. Vaughan wrote: >> it looks like doing so effectively deprecates Solaris 7 support > > That's fine. Sun (now Oracle) stopped supporting Solaris 7 > in August 2008. Even Solaris 8 is fair game now; its end

Re: maint.mk bug (with tentative fix)

o avoid crashing the detecting make process)? Add an m4 macro to the maintainer-makefile module that gets added to every maint.mk project's configure by gnulib-tool? Hopefully you have something in mind with less overhead than either of those? Cheers, -- Gary V. Vaughan (gary AT gnu DOT org) signature.asc Description: Message signed with OpenPGP using GPGMail

as_echo/bs_echo still required?

I'll provide the patches if there is a consensus to apply them. But, it looks like doing so effectively deprecates Solaris 7 support, which may be premature... Comments? Cheers, -- Gary V. Vaughan (gary AT gnu DOT org) signature.asc Description: Message signed with OpenPGP using GPGMail

Re: maint.mk bug (with tentative fix)

Hi Jim, Thanks for the quick response. On Jan 2, 2014, at 2:27 PM, Jim Meyering wrote: > On Wed, Jan 1, 2014 at 5:08 PM, Gary V. Vaughan wrote: > ... >> The change (back ticks instead of $(...) in the no-submodule-changes rule) >> looks like a harmless way to fix the bug

maint.mk bug (with tentative fix)

se\ : ; \ fi The change (back ticks instead of $(...) in the no-submodule-changes rule) looks like a harmless way to fix the bug to me. Okay to push? Cheers, -- Gary V. Vaughan (gary AT gnu DOT org) signature.asc Description: Message signed with OpenPGP using GPGMail

Re: Version number tag

a fair shot at working even in a shallow cloned gnulib subproject - otherwise certain invocations of bootstrap can break the release rules in maint.mk. Jim plans to push a version tag every 1000 commits or so. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: gnulib-v0.1: a non-event

Hi Jim, On Oct 30, 2013, at 10:13 AM, Jim Meyering wrote: > On Tue, Oct 29, 2013 at 1:21 PM, Gary V. Vaughan wrote: >> for now the new tag and fallback to --short-log fixes all >> the immediate problems I was having (except the reliance on gnupg-1.4 >> gpgv). > > Yo

Re: gnulib-v0.1: a non-event

wrong. I'll fix that later, but for now the new tag and fallback to --short-log fixes all the immediate problems I was having (except the reliance on gnupg-1.4 gpgv). Cheers, -- Gary V. Vaughan (gary AT gnu DOT org) signature.asc Description: Message signed with OpenPGP using GPGMail

Re: gnulib-v0.1: a non-event

n easy solution to the shallow clone issue with bootstrap, by making sure the shallow clones are at least 1000 changesets deep. WDYT? Cheers, -- Gary V. Vaughan (gary AT gnu DOT org) signature.asc Description: Message signed with OpenPGP using GPGMail

Re: [PATCH] maint.mk: get current gnulib revision correctly.

about that. Gnulib is the last project I contribute to that has a manually maintained ChangeLog, so I’m out of the habit. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org) signature.asc Description: Message signed with OpenPGP using GPGMail

Re: [PATCH] maint.mk: get current gnulib revision correctly.

Hi Bruce, On Oct 29, 2013, at 4:45 AM, Bruce Korb wrote: > On 10/27/13 17:46, Pádraig Brady wrote: >>> gnulib_dir ?= $(srcdir)/gnulib >>> -gnulib-version = $$(cd $(gnulib_dir) && git describe) >>> +gnulib-version = $$(cd $(gnulib_dir) && git rev-parse --short HEAD) >>> bootstrap-tools ?= autoc

Re: [PATCH] maint.mk: get current gnulib revision correctly.

int.mk rules. If you disagree strongly, please feel free to revert on my behalf. Cheers, — Gary V. Vaughan (gary AT gnu DOT org) signature.asc Description: Message signed with OpenPGP using GPGMail

Re: [PATCH 2/2] do-release-commit-and-tag: use funclib.sh instead of sort -V GNUism.

$prev_ver)" > > which is simpler and is more robust in the presence of > oddities like spaces in version numbers. Agreed. Also applied. On balance, I picked a poor time to submit useful bits of libtool to gnulib, since I’m starting to get feedback on the prerelease which is producing some churn in the funclib.sh and others. I’ll wait for the testing to finish, and then resubmit what I have then. Cheers, — Gary V. Vaughan (gary AT gnu DOT org) signature.asc Description: Message signed with OpenPGP using GPGMail

[PATCH 2/2] do-release-commit-and-tag: use funclib.sh instead of sort -V GNUism.

* build-aux/do-release-commit-and-tag: Source funclib.sh from the same directory as do-release-commit-and-tag, and then call the func_sort_ver shell function in lieu of unportable sort -V. Signed-off-by: Gary V. Vaughan --- build-aux/do-release-commit-and-tag | 10 ++ 1 file changed, 6

[PATCH] new funclib.sh module

enhance gnulib-tool to inline funclib.sh during copying, but I just realised that before I can push this simplified version I need to add funclib.sh to the Depends: block in modules/do-release-commit- and-tag. Okay to push (one or both)? Cheer, -- Gary V. Vaughan (gary AT gnu DOT org)

[PATCH 1/2] funclib.sh: new module, shell script boiler plate and helper fns.

: Gary V. Vaughan --- build-aux/funclib.sh | 1212 ++ modules/funclib.sh | 19 + 2 files changed, 1231 insertions(+) create mode 100644 build-aux/funclib.sh create mode 100644 modules/funclib.sh diff --git a/build-aux/funclib.sh b/build-aux

Re: [PATCH] maint.mk: get current gnulib revision correctly.

On Oct 27, 2013, at 1:06 PM, Paul Eggert wrote: > Thanks, that looks good, please push. Thanks. Pushed. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org) signature.asc Description: Message signed with OpenPGP using GPGMail

[PATCH] maint.mk: get current gnulib revision correctly.

Further to my earlier bug report. Okay to push? * top/maint.mk (gnulib-version): Use git rev-parse to get the current HEAD revision. Signed-off-by: Gary V. Vaughan --- top/maint.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/top/maint.mk b/top/maint.mk index c1b786f

maint.mk bug

$ cd gnulib $ git describe fatal: No names found, cannot describe anything. I will finish the release process by hand, but wanted to ping the list so that the bugs don't get forgotten :) Cheers, -- Gary V. Vaughan (gary AT gnu DOT org) signature.asc Description: Message signed with OpenPGP using GPGMail

Re: [ANN] m4-1.4.17 released [stable]

Hi Eric, On Sep 24, 2013, at 10:07 AM, Eric Blake wrote: > On 09/23/2013 09:28 AM, Gary V. Vaughan wrote: >> >> Clearly, it should at least check whether the compiler is actually gcc >> before piling >> on the flags, although I don't think it is serious enoug

Re: [ANN] m4-1.4.17 released [stable]

log. > When I disable using git in our buildsystem > the compilation works fine. I would prefer a system that enabled flags > explicitly and not by inspecting side effects but I can understand the > current behaviour. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org) signature.asc Description: Message signed with OpenPGP using GPGMail

Re: [bug #35580] bootstrap is not portable to OpenBSD

Hi Mike, Thank you for taking the time to try my script, and especially for the great feed back. Much appreciated! On Aug 9, 2013, at 8:33 PM, Mike Miller wrote: > On Fri, Aug 9, 2013 at 10:36:42 +0700, Gary V. Vaughan wrote: >> >> I'd be delighted to hear your feed

Re: [bug #35580] bootstrap is not portable to OpenBSD

required: $_G_find_tool_names" fi } The invocation for finding a SHA1SUM setting says: # Find sha1sum, named gsha1sum on MacPorts, and shasum on MacOS 10.6+. func_find_tool SHA1SUM sha1sum gsha1sum shasum I'd be delighted to hear your feedback if you have any success in switching to my rewrite. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: test-fclose coredumps on AIX 5 thru 7 (and similar test-strtod coredump on ia64)

Hi Paul, On 11 Mar 2013, at 21:55, Paul Eggert wrote: > On 03/11/2013 12:35 AM, Gary V. Vaughan wrote: >> Anything I can do to help debug this failure? > > That looks like an AIX bug, no? Perhaps file a bug with IBM? > > I'm not sure it's gnulib's job to w

test-fclose coredumps on AIX 5 thru 7

o to help debug this failure? Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: [PATCH] make check failure on Tru64 Unix

Hi Paul, On 11 Mar 2013, at 12:31, Paul Eggert wrote: > On 03/10/2013 10:18 PM, Gary V. Vaughan wrote: >> Any objections if I push the fix? > > No, thanks, that fix looks good to me. Pushed. Thank you. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

[PATCH] make check failure on Tru64 Unix

include # undef __need_system_stdlib_h After reconfiguring and building with this patch, m4 now picks up the working gnulib strtod: tru64% src/m4 format(`%g', `0xa.P+1') 20 And the full testsuite (gnulib tests and all) p

Re: Test failure on Mac OS 10.8.2

Hi Paul, Thanks for applying a fix so quickly. On 9 Mar 2013, at 00:47, Paul Eggert wrote: > On 03/08/2013 09:15 AM, Gary V. Vaughan wrote: > >> ../../tests/test-xvasprintf.c: In function 'test_xasprintf': >> >> ../../t

Re: Test failure on Mac OS 10.8.2

Hi Paul, Thanks for the quick response. On 9 Mar 2013, at 00:04, Paul Eggert wrote: > On 03/08/2013 08:43 AM, Gary V. Vaughan wrote: >> Anything else I can do to help fix this? > > Can you tell us what my_asprintf is putting into 'result'? If I print result just

Test failure on Mac OS 10.8.2

free (result); 241 } Anything else I can do to help fix this? Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: bootstrap: Portability issue on FreeBSD.

NU Zile, lua-stdlib, luaposix and others), which doesn't hardcode the 'sh' invocation anywhere. The newest online version of bootstrap right now is available here: http://git.savannah.gnu.org/cgit/m4.git/plain/bootstrap?h=branch-1.4 Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

[FYI] regex: rename remaining __attribute calls to __attribute__.

From: "Gary V. Vaughan" Commit 930b85b changed definition of __attribute, but left some uses unchanged, preventing compilation of regex module on most non-gcc environments: * lib/regcomp.c (re_set_fastmap, seek_collating_symbol_entry) (lookup_collation_sequence_value, build

Re: Documentation of lib$package.a?

Hi Reuben, On 31 Jan 2013, at 00:37, Reuben Thomas wrote: > On 30 January 2013 17:10, Gary V. Vaughan wrote: >> Are you using the bootstrap script from gnulib (which I didn't check) > > Yes. Then, may I humbly suggest you switch to my bootstrap rewrite, which has behavi

Re: Documentation of lib$package.a?

g gnulib_name somehow from bootstrap.conf? Quickly testing latest gnulib-tool, it already shows a reminder to set _LDADD or _LDFLAGS appropriately. It seems your environment is not working properly. HTH, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: You may need to add #include directives for the following .h files

ion was active for every xtrace entry. Good tip! Thanks :) Once upon a time I also wrote a full interactive debugger for bash (full disclosure: I cribbed a lot of it from the ORA ksh book, with permission), which I think is still included in the distribution. However, I've taken to writi

Re: [PATCH] bootstrap: remove the need for a sorted .gitignore

Hi Jim, On 28 Jan 2013, at 09:52, Jim Meyering wrote: > Gary V. Vaughan wrote: > ... >>>>> so it would be safer to probe for >>>>> and use a backslash safe echo here >>>>> >>>> Much better would be to just use printf. Safer, sim

Re: [PATCH] bootstrap: remove the need for a sorted .gitignore

s where I default to old-school portability, and might be obfuscating my scripts unnecessarily if I'm inadvertently pandering to museum pieces, and until someone kindly points me to the evidence of my errors I'm not even aware of where all those opportunities to improve and modernize will lie. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: [PATCH] bootstrap: remove the need for a sorted .gitignore

; Addressing them are probably best for a subsequent patch. Agreed, though practically speaking, I fear that subsequent patch will not arrive :( > On 01/26/2013 05:27 AM, Gary V. Vaughan wrote: >> Here is the version I've added to libtool bootstrap (note, the arguments >> are

Re: You may need to add #include directives for the following .h files

ool_base_options function out just now in latest libtool master HEAD of bootstrap in order to avoid having to copy the gnulib-tool option setting code out of bootstrap into the functions above. It may work for you anyway, provided that you are already using the gnulib-tool defaults for --aux-dir, --m4-base, --doc-base, --lib, --local-dir and --source-base, but I'd recommend pulling the latest libtool bootstrap just to be future-proof. :) HTH, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: [PATCH] bootstrap: remove the need for a sorted .gitignore

&& func_error "duplicate entries in $file: " $duplicate_entries func_grep_q "$str" "$file" \ && func_verbose "inserting '$str' into '$file'" linesold=`func_gitignore_entries "$file" |wc -l` linesnew=`$bs_echo "$str" \ |func_gitignore_entries - "$file" |sort -u |wc -l` test $linesold -eq $linesnew \ || sed "1i\\$nl$str$nl" "$file" \ || func_permissions_error "$file" done } Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

[PATCH 2/2] gitlog-to-changelog: remove duplicates without warning messages.

From: "Gary V. Vaughan" Now, when the new 'Omit-from-ChangeLog: Yes' tag is found in a commit log entry, after git-log-fix edits have been applied, don't output anything into the ChangeLog for that entry. * bulid-aux/gitlog-to-changelog: Omit-from-ChangeLog is a

[PATCH 1/2] gitlog-to-changelog: don't output spurious header lines.

From: "Gary V. Vaughan" Move the code for printing header lines inside the else clause of the empty commit message warning if... so you either get a warning, or you get the ChangeLog header followed by the non-empty commit message. * build-aux/gitlog-to-changelog: When there is

[PATCH 0/2] gitlog-to-changelog remove duplicate log entries

-changelog patch * gl/build-aux/gitlog-to-changelog.diff: Delete. 2012-02-19 Gary V. Vaughan 2012-02-02 Roumen Petrov(tiny change) fixup: restore EXPORTS test With the first patch applied, gitlog-to-changelog continues to issue the empty commit warning, but doesn&

Re: bootstrap does not pass --force to autoreconf

Salut Akim! On 28 Dec 2012, at 19:22, Akim Demaille wrote: > Le 28 déc. 2012 à 12:39, "Gary V. Vaughan" a écrit : >> On 28 Dec 2012, at 18:00, Akim Demaille wrote: >>> Can't all these bootstraps be merged? Bison used to have a forked >>> one too, but

Re: bootstrap does not pass --force to autoreconf

On 28 Dec 2012, at 18:00, Akim Demaille wrote: > Le 28 déc. 2012 à 10:35, "Gary V. Vaughan" a écrit : >> Salut Akim! > > Hi Gary! Long time no see :) Too long! :) >> My bootstrap rewrite (used by Libtool & Zile among others) has always >> passed any `

Re: bootstrap does not pass --force to autoreconf

ite (used by Libtool & Zile among others) has always passed any `--force' from it's own command line along to all autoreconf and libtoolize invocations it makes without any problems. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: error: required file 'config.h.in' not found

ent fixes in it: http://git.savannah.gnu.org/cgit/libtool.git/plain/bootstrap Do you have a repo or tarball of your source package I can look at to try and reproduce? Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: Patches to README-release

Hi Jim, On 28 Jan 2012, at 16:28, Jim Meyering wrote: > Gary V. Vaughan wrote: >> I'm wondering what purpose AC_PREREQ (etc) really >> serves if you're not using them to encode the versions of the autotools that >> are >> required to bootstrap a package i

Re: Patches to README-release

Hi Jim, On 28 Jan 2012, at 15:27, Jim Meyering wrote: > Gary V. Vaughan wrote: >> Hi Jim, >> >> On 28 ม.ค. 2012, at 1:21, Jim Meyering wrote: >> >>Reuben Thomas wrote: >> >>Ping? The patches still apply cleanly to HEAD. >> >&g

Re: Patches to README-release

e addition of this paragraph in README-release, which Reuben has correctly noted as spurious (when using saner bootstrap)? P.S. I will repropose saner bootstrap and supporting scripts to gnulib when my workload eases off in a few more weeks, as I promised last year. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: [PATCH] bootstrap: remove some now-unneeded code

the whole project by default, including subprojects, so that there is no need to step into each subproject and bootstrap it by hand. Libtool's bootstrap.conf is set up to automatically descend into 10 subprojects, and adds additional options to bootstrap to manage skipping some or all

Re: issues with git submodules and `bootstrap'

of gnulib style bootstrap.conf Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: issues with git submodules and `bootstrap'

Hi Simon, On 11 Jan 2012, at 22:08, Simon Josefsson wrote: > "Gary V. Vaughan" writes: >> Now that I think about it, I'd like to put the multi-gnulib support >> directly into my bootstrap script so that it can be called by setting >> some configuration var

Re: issues with git submodules and `bootstrap'

Hi Simon, On 11 Jan 2012, at 21:35, Gary V. Vaughan wrote: > On 11 Jan 2012, at 20:57, Simon Josefsson wrote: >> [[...]] for some reason, my projects >> often follow a pattern where they need to have multiple gnulib >> instances. > > [[...]] I think this setup is

Re: issues with git submodules and `bootstrap'

to go ahead and try my bootstrap script, and finish the multi-gnulib instance hook function without any help, please ping me afterwards if you don't mind me adopting it for M4 too :) Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: issues with git submodules and `bootstrap'

ing so radical and progressive as well =)O| Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: issues with git submodules and `bootstrap'

ful acceptance as a replacement for the existing script. Since then, I've broken out some functionality into reusable standalone scripts that will be useful for replacing the hairy sed-and-grep method of interrogating the m4 macros used by configure.ac with a much more robust and faster call to parse the m4 macros with GNU M4! I'll submit that script presently, and the hook-and-require infrastructure file it depends on. If we can agree on accepting those into upstream, I'll start posting the bootstrap rewrite contents for review a few functions at a time. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: issues with git submodules and `bootstrap'

ir=../gnulib or similar if you prefer) simply does the right thing. The rewrite is compatible with the bootstrap.conf format of the gnulib bootstrap script, but is much easier to extend without any ugly hacks. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: [PATCH] gitlog-to-changelog: Copyright-paperwork-exempt: yes == (tiny change)

e, so > I'll wait for an ACK before I push. That's great! Please go right ahead :-) Cheers, Gary > Jim > > From 9301160f1f63d1193402a4cecf17c33da2305020 Mon Sep 17 00:00:00 2001 > From: "Gary V. Vaughan" > Date: Fri, 30 Dec 2011 18:47:55 +0100 > Subj

Avoiding namespace-pollution when adding gnulib modules to libltdl?

bltdl has to be compiled with its own subconfigure, Makefile, build-aux and macro dirs. But that's a lot of extra weight, duplication of code and is an arbitrary restriction I'd rather avoid if it can be done without too much effort. Any pointers or clues very much appreciated. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

HOWTO: track '(tiny change)' in gitlog-to-changelog generated ChangeLog

ains an up-to-date copy in its own git repo, and that should still be available from here (even if you are from the future, as long as it's not too far from now anyway): http://git.savannah.gnu.org/cgit/libtool.git/plain/gl/build-aux/gitlog-to-changelog.diff In the worst case, you might ne

Re: [PATCH 1/2] gitlog-to-changelog: support multi-author commits.

Hi Jim, Thanks for the reviews. On 17 Nov 2011, at 03:01, Jim Meyering wrote: > Gary V. Vaughan wrote: > ... >> the parts that didn't work OOTB on my Mac to be portable. Feel free to crib >> those portable parts of this one into coreutils, or reformat this one to &g

Re: [PATCH 2/2] gitlog-to-changelog: support 'tiny change' commits.

Hi Jim, On 15 Nov 2011, at 20:10, Jim Meyering wrote: > Gary V. Vaughan wrote: >> On 15 Nov 2011, at 19:02, Jim Meyering wrote: >>> Propose a patch to maintain.texi. >> >> I don't want to get into a debate over the merits of generated >> ChangeLogs with

Re: [PATCH] maint.mk: fix tight-scope.mk generation in VPATH builds.

Hi Jim, On 15 Nov 2011, at 20:14, Jim Meyering wrote: > Gary V. Vaughan wrote: >> Okay to push? >> >> * top/maint.mk (tight-scope.mk): Make sure to prefix file >> reference with $(srcdir) so that the file is found correctly even >> when running `ma

Re: [PATCH 2/2] gitlog-to-changelog: support 'tiny change' commits.

Hi Jim, On 15 Nov 2011, at 19:02, Jim Meyering wrote: > Gary V. Vaughan wrote: >> On 15 Nov 2011, at 18:14, Jim Meyering wrote: >>> Gary V. Vaughan wrote: >>>> I think 'Copyright-paper-required: No' is still the best compromise here >>>> for &g

Re: [PATCH 2/2] gitlog-to-changelog: support 'tiny change' commits.

Hi Jim, On 15 Nov 2011, at 18:14, Jim Meyering wrote: > Gary V. Vaughan wrote: >> I think 'Copyright-paper-required: No' is still the best compromise here for >> the reasons stated earlier in the thread. >> >> Okay to push? >> >> The FSF requir

[PATCH] maint.mk: fix tight-scope.mk generation in VPATH builds.

Okay to push? * top/maint.mk (tight-scope.mk): Make sure to prefix file reference with $(srcdir) so that the file is found correctly even when running `make syntax-check' in a VPATH build. Signed-off-by: Gary V. Vaughan --- ChangeLog|7 +++ top/maint.mk |2 +- 2 files ch

Re: [PATCH 1/2] gitlog-to-changelog: support multi-author commits.

I omitted the ChangeLog and git log entry for the commit-msg script, now fixed in my private branch as follows: On 15 Nov 2011, at 12:04, Gary V. Vaughan wrote: > > The FSF cares about keeping track of all authors of patches to its > projects, but Git doesn't provide obvious sup

Re: [PATCH 2/2] gitlog-to-changelog: support 'tiny change' commits.

e, since the size of the >>> change is already known, via the associated patch. >> >> Gary V. Vaughan wrote: >> This is a confusion brought about by the 'Tiny change' misnomer I think. If >> it were a simple matter of counting lines, then you would be ent

Re: [PATCH 1/2] gitlog-to-changelog: support multi-author commits.

Hi Jim, Sorry for the long wait. With the flooding in Bangkok affecting everything, I've had very spotted access to the Internet, otherwise I would have responded sooner. On 1 Nov 2011, at 20:09, Jim Meyering wrote: > Gary V. Vaughan wrote: >> More generally useful gnulib-local

Re: [PATCH 1/4] ptsname_r: new module

x27;s redundant when you already state the version number, 10.5. On 10 Nov 2011, at 05:39, Bruno Haible wrote: > Gary V. Vaughan wrote: >> Although it is common to see, e.g. Mac OS X 10.5 in writing, it's >> redundant and technically incorrect. > > Possibly. But whe

Re: [PATCH 2/2] gitlog-to-changelog: support 'tiny change' commits.

hangeLog is set in stone, but I'd like to take the opportunity here to choose a less confusing tag to put in git (which will likely be what the patch submitter sees in the commit emails their patch generates, or by running git diff). >>> Even if somewhere you've felt "insistence" on this issue, >>> let's just write "request": > > "(tiny change)" is more than a request. That is my impression too. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: [PATCH 2/2] gitlog-to-changelog: support 'tiny change' commits.

Ping Karl... Depending on your thoughts, I will resubmit this patch series for gnulib rather than keeping the patches solely in Libtool's tree. On 1 Nov 2011, at 20:56, Gary V. Vaughan wrote: > On 1 Nov 2011, at 20:13, Jim Meyering wrote: >> Gary V. Vaughan wrote: >>> >

Re: [PATCH 1/4] ptsname_r: new module

int five" :( Irrespective of that, outside of Apple, you see the incorrect spacing and doubling of `ten' frequently, so no one will misunderstand those mis-spellings :) Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: [PATCH 2/2] gitlog-to-changelog: support 'tiny change' commits.

Hi Jim, Karl, On 1 Nov 2011, at 20:13, Jim Meyering wrote: > Gary V. Vaughan wrote: >> >> diff --git a/ChangeLog b/ChangeLog >> index f370be6..d59d9f9 100644 >> --- a/ChangeLog >> +++ b/ChangeLog >> @@ -1,5 +1,14 @@ >> 2011-11-01 Gary V. Vaughan &

[PATCH 2/2] gitlog-to-changelog: support 'tiny change' commits.

+++-- 2 files changed, 17 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index f370be6..d59d9f9 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,14 @@ 2011-11-01 Gary V. Vaughan + gitlog-to-changelog: support `tiny change' commits. + The FSF insist

[PATCH 1/2] gitlog-to-changelog: support multi-author commits.

prev_date_line) + + # Format 'Co-authored-by: A U Thor ' lines in + # standard multi-author ChangeLog format. + my @coauthors = grep /^Co-authored-by:.*>$/, @line; + s/^Co-authored-by:\s*([^<]+)\s+$/, @line; + # Omit "Co-authored-by..." and "S

Re: [PATCH 3/3] maint: use gnulib's gitlog-to-changelog instead of a ChangeLog file.

Hi Peter, On 31 Oct 2011, at 22:24, Peter Rosin wrote: > Gary V. Vaughan skrev 2011-10-23 18:17: >> We already have to enter all the ChangeLog relevant information into the git >> commit log. Instead of worrying about keeping them all in sync, this patch >> generates the c

Re: [PATCH] GNUmakefile: reenable "make syntax-check" for most projects

> to precede inclusion of maint.mk. Otherwise, these variables would > be used undefined in any project that does not override the default. Oh, ouch. Sorry about that. I should have tested without a cfg.mk override before submitting, but didn't think to look because it was working fine in my tree without the patch. My bad. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

Re: [PATCH] maint.mk: don't maintain a second build-aux variable.

Hi Jim, On 27 Oct 2011, at 22:02, Jim Meyering wrote: > Gary V. Vaughan wrote: >> On 25 Oct 2011, at 15:18, Gary V. Vaughan wrote: >>> On 25 Oct 2011, at 15:05, Jim Meyering wrote: >>>> Actually, I think we can both get what we want. >>>> I suggest to ad

Re: [PATCH] maint.mk: don't maintain a second build-aux variable.

Hi Jim, On 25 Oct 2011, at 15:18, Gary V. Vaughan wrote: > On 25 Oct 2011, at 15:05, Jim Meyering wrote: >> Actually, I think we can both get what we want. >> I suggest to adjust your patch so that make is guaranteed to fail >> with a nice diagnostic for anyone who define

Re: [PATCH] maint.mk: don't maintain a second build-aux variable.

e mail I'll be very happy to hear about it... in the mean time, I'll try to remember not to reply to bug-gnulib on my iPad over morning coffee. > Gary V. Vaughan wrote: >> To what advantage over factoring out the duplication entirely at the >> source of the problem with

Re: [PATCH] maint.mk: don't maintain a second build-aux variable.

Hi Jim, On 25 Oct 2011, at 00:37, Jim Meyering wrote: > Gary V. Vaughan wrote: >> >> _build-aux = libltdl/build-aux > > Wouldn't that break things for those who customize build_aux? Ah, I see what you mean now (will it break for clients who are customizing with

Re: [PATCH] maint.mk: don't maintain a second build-aux variable.

Hi Jim, On 25 Oct 2011, at 00:37, Jim Meyering wrote: > Gary V. Vaughan wrote: >> I was wondering why 'make stable' would always use a stale version unless >> I manually updated my .version file first. It turns out that if you use >> a non-standard build

[PATCH] maint.mk: don't maintain a second build-aux variable.

@ 2011-10-23 Gary V. Vaughan + + maint.mk: don't maintain a second build-aux variable. + * maint.mk (build_aux): Removed. The maintainer-makefile module + depends on GNUmakefile, which already maintains a cfg.mk + overridable $(_build-aux) for projects with

Re: [PATCH] README-release improvements

Hi Stefano, On 23 Oct 2011, at 00:20, Stefano Lattarini wrote: > Hi everybody. Just my two cents about this matter ... > > On Saturday 22 October 2011, Bruno Haible wrote: >> Gary V. Vaughan wrote: >>>>> Running the (potentially) outdated configure, to build

Re: [PATCH] README-release improvements

Hi Jim, On 22 Oct 2011, at 17:15, Jim Meyering wrote: > Gary V. Vaughan wrote: >> >> If you want to clean the cruft out of your working directories before >> starting the release process, you should do it before you change branches >> and merge changes from upstream,

Re: [PATCH] README-release improvements

Hi Jim, On 22 Oct 2011, at 03:06, Jim Meyering wrote: > Gary V. Vaughan wrote: >> As it stands (without this patch), README-release recommends: >> >> git checkout master >> git pull >> ./configure >> make maintainer-clean >> ./bootstrap >&g

Re: [PATCH] README-release improvements

Hi Jim, On 21 Oct 2011, at 15:17, Jim Meyering wrote: > Gary V. Vaughan wrote: >> I made these changes in gnulib-local/top/README-release while making >> a start at leveraging the gnulib release machinery into GNU Libtool, >> but they seem generally applicable too. > >

Re: [PATCH] README-release improvements

had misremembered my old bash-2.05 doing it that way, but I've long since moved to a zsh login shell which doesn't have that problem. I'll remove that and repost after addressing Jim's review too. Cheers, -- Gary V. Vaughan (gary AT gnu DOT org)

  1   2   3   4   >