* build-aux/update-copyright: Add support for Emacs, which
uses file names like Changelog.1 that are not man pages,
and file names like emacs.1.in that are man page templates.
---
ChangeLog | 7 +++
build-aux/update-copyright | 4 ++--
2 files changed, 9 insertions(+), 2
Before upgrading to Unicode 15.1.0, it's also required to update the copyright
year in the generated files.
2024-01-30 Bruno Haible
gen-uni-tables: Update copyright year in output.
* lib/gen-uni-tables.c (output_predicate_test, output_predicate,
output_cat
Since 2011, the yearly 'update-copyright' did not update the copyright years
of the files in tests/unictype/. But there is no reason for this. (Maybe in
2011 the majority of the files were autogenerated? This is not the case
any more.) As a consequence, the files
tests/unictype/test-ca
--?|\\\(en))
+ ((??{
+ .../ at
/Users/bruno/data/build/testdir-all/build-aux/update-copyright line 243, <>
chunk 1.
FAIL test-update-copyright.sh (exit status: 1)
On this system, perl is v5.8.8.
Pádraig Brady reported the same test failure on CentOS 7, with perl v
On Tue, Jan 10, 2023 at 8:37 PM Jim Meyering wrote:
> FYI, I've just pushed this fix.
> I noticed this bug when attempting to update gzip's copyright dates.
> It has a few files with two copyright lines.
> The old version of this script would update only the first one.
For the record, that fix ad
001
From: Jim Meyering
Date: Mon, 2 Jan 2023 22:52:08 -0800
Subject: [PATCH] update-copyright: also work with two or more updatable lines
in a file
* build-aux/update-copyright: Replace every occurrence of the copyright
line, not just the first one.
* tests/test-update-copyright.sh: Add a test
d by Simon Joseffson in:
https://lists.gnu.org/r/bug-gnulib/2022-12/msg00125.html
* Makefile (COPYRIGHT_TZ): New macro.
(update-copyright): Use it.
---
ChangeLog | 8
Makefile | 7 +++
2 files changed, 15 insertions(+)
diff --git a/ChangeLog b/ChangeLog
index ef7f457143..8ef7d0c
> * doc/gendocs_template: Change 2020 to 2022.
Thanks. Applied.
* doc/gendocs_template: Change 2020 to 2022.
---
doc/gendocs_template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/gendocs_template b/doc/gendocs_template
index c8c8fc610010..0415d947be65 100644
--- a/doc/gendocs_template
+++ b/doc/gendocs_template
@@ -87,7 +87,7 @@ the
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,14 @@
+2022-01-27 Paul Eggert
+
+ maint: Update copyright notices
+ * build-aux/announce-gen, build-aux/declared.sh:
+ * build-aux/git-version-gen, build-aux/gitlog-to-changelog:
+ * build-aux/gnu-web-doc-update, build-aux/gnupload
After running ‘make update-copyright’ I noticed that it
incorrectly replaced a couple of symlinks with their contents.
* Makefile (update-copyright): Do not update symlinks.
* etc/license-notices/GPL, etc/license-notices/LGPL:
Change these back to symlinks.
---
ChangeLog| 9
On Sat, Jan 4, 2020 at 11:15 PM Bruno Haible wrote:
> > Here's another that I'll push tomorrow:
>
> Oops, right. My mistake. Like in build-aux/update-copyright, you might also
> want to restore the -0777 option that was lost on 2019-06-15.
Thanks, but while that option
Hi Jim,
> Here's another that I'll push tomorrow:
Oops, right. My mistake. Like in build-aux/update-copyright, you might also
want to restore the -0777 option that was lost on 2019-06-15.
Bruno
Here's another that I'll push tomorrow:
always-skipped-update-copyright-test.diff
Description: Binary data
Before doing the following changes done by hand, I also ran ‘make
update-copyright’ and ‘config/srclist-update
+
+ maint: update copyright notices
+ Before doing the following changes done by hand, I also ran ‘make
+ update-copyright’ and ‘config/srclist-update
uchar
---
ChangeLog | 6 --
build-aux/update-copyright | 14 --
2 files changed, 12 insertions(+), 8 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index ae7adbbd5..db63a4be0 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,8 +1,10 @@
2019-10-14 Paul Eggert
* build-aux/update-copyright: Match year ranges like "1998--2019",
which are used in the Autoconf manual.
---
ChangeLog | 6 ++
build-aux/update-copyright | 2 +-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/ChangeLog b/ChangeLog
index d27674fa6.
Bernhard Voelker wrote:
> Hmm, and what about the other changes of perl options in commit a05d5d121b10:
>
> * build-aux/useless-if-before-free:
> had tainting checks enabled (-T):
>
> < eval 'exec perl -wST "$0" "$@"'
> > eval 'exec perl -wSx "$0" "$@"'
The benefit of this "taint mode" was
On 7/16/19 10:03 AM, Bruno Haible wrote:
> Thanks for the report. Indeed, a bad regression. Fixed as follows:
Hmm, and what about the other changes of perl options in commit a05d5d121b10:
* build-aux/useless-if-before-free:
had tainting checks enabled (-T):
< eval 'exec perl -wST "$0" "$@"'
Hi,
Brian C. Lane wrote:
> I think it was the change in commit a05d5d121b10f24 where it moved and
> changed the exec code at line 1.
>
> In parted with the latest gnulib I am getting these errors with 'make
> update-copyright'
>
> GEN update-copyright
>
I think it was the change in commit a05d5d121b10f24 where it moved and
changed the exec code at line 1.
In parted with the latest gnulib I am getting these errors with 'make
update-copyright'
GEN update-copyright
Use of uninitialized value $_ in pattern match (m//) at
./build-
Mathieu Lirzin wrote:
> +2018-01-04 Mathieu Lirzin
> +
> + update-copyright: Handle use of ©
> + * build-aux/update-copyright ($circle_c_re): Update regex to
> + handle use of © in headers.
Thanks. Applied. And I added a 'coding: utf-8' marker to this fi
* build-aux/update-copyright ($circle_c_re): Update regex to
handle use of © in headers.
---
ChangeLog | 6 ++
build-aux/update-copyright | 5 +++--
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 3f2d8ce..13e868a 100644
--- a
Thanks for doing that. It can be a challenge improving programs that are run
only once a year. I'm reminded of the Long Now's clock:
http://longnow.org/clock/
which has even longer-term debugging issues.
pdate-copyright" would now also induce the changes
of d9afeacd0e2396deaabab291ab94e09ab9834fdb.
I'll push this tomorrow:
Subject: [PATCH] update-copyright: add code to handle more special cases
After running "make update-copyright" this year, five files
required additional manual
() Karl Berry
() Mon, 23 May 2016 20:56:23 GMT
[get around ‘-i’ somehow] (see perlrun)
Thanks.
On the other hand, I wouldn't argue that --help/--version
support is so important for this script that it is worth any
complication (let alone a wrapper).
I agree, it's not so important.
was defeated by Perl's ôòø-iôòù support (which, IIUC, says to take all
script args as filenames, hence leaving no room for the script to
check/handle args specially
Untried, but what comes to mind first is to check if ($ARGV eq "--help").
Or, omit the -i,
check for --help/--version,
For anyone interested, here is a small update-copyright wrapper
that supports ‘--help’ and ‘--version’:
#!/bin/sh
actual=$HOME/build/GNU/gnulib/build-aux/update-copyright
if [ x"$1" = x--help ] ; then
printf 'Usage: %s FILE...\n\n' `basename $0`
sed -e '/argumen
Jim Meyering wrote:
Ironic, indeed.
Do you know how it was missed the first time?
I suspect you cloned or updated gnulib in 2014, then made a change in a private
copy, then on Jan 1 I ran 'make update-copyright' and pushed
b9bfe78424b871f5b92e5ee9e7d21ef951a6801d, then this year
On Thu, Jan 15, 2015 at 12:57 PM, Paul Eggert wrote:
> * build-aux/update-copyright: Fix copyright date. How ironic!
> ---
> ChangeLog | 5 +
> build-aux/update-copyright | 4 ++--
> 2 files changed, 7 insertions(+), 2 deletions(-)
...
> -# Copyright
* build-aux/update-copyright: Fix copyright date. How ironic!
---
ChangeLog | 5 +
build-aux/update-copyright | 4 ++--
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index e00ea17..d1e878a 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3
I've just pushed these two changes:
test-strstr.c: avoid a trivial leak
* tests/test-strstr.c (main): Free haystack.
update-copyright: recognize groff's \(co marker
* build-aux/update-copyright (circle_c_re): Also accept
uses of \(co, as found
with gaps in the years,
>>> but no spaces in the listing) is not currently tested in the
>>> update-copyright testsuite.
>>
>> I don't believe the "no spaces" is required for this bug to show. The
>> corruption also appeared for misc/sys/file.h, f
he listing) is not currently tested in the
>> update-copyright testsuite.
>
> I don't believe the "no spaces" is required for this bug to show. The
> corruption also appeared for misc/sys/file.h, for example:
>
> -/* Copyright (C) 1991, 92, 96, 97, 98, 99 Free Softw
On Wed, 2 Jan 2013, Eric Blake wrote:
> The original was:
>
>Copyright (C) 1995,97,99 Free Software Foundation, Inc.
>
> and that pattern (4-digits followed by 2-digits, with gaps in the years,
> but no spaces in the listing) is not currently tested in the
> update-co
On 01/02/2013 12:31 PM, Joseph S. Myers wrote:
> A second check of the automatic copyright updates for glibc showed that
> update-copyright had corrupted some of the copyright notices. I've
> applied this glibc patch to fix that corruption. bug-gnulib: see
> attachment for
A second check of the automatic copyright updates for glibc showed that
update-copyright had corrupted some of the copyright notices. I've
applied this glibc patch to fix that corruption. bug-gnulib: see
attachment for a testcase. Run update-copyright as:
UPDATE_COPYRIGHT_FO
ile because there was a
>>> release every year. If this is illegal or bad practice, it would be
>>> useful if you could share your response from the FSF.
>>
>> For everyone's benefit, the FSF confirmed that it is fine to do so
>> (case [gnu.org #719834
his is illegal or bad practice, it would be
>> useful if you could share your response from the FSF.
>
> For everyone's benefit, the FSF confirmed that it is fine to do so
> (case [gnu.org #719834]).
Thanks. Here's an adjusted version of update-copyright that
implemen
Joel Brobecker writes:
>> > Yep, this is what we did for this year. I just want to go one step
>> > further and just collapse all years into one single range, based on
>> > the fact that I have verified that we have made significant changes
>> > to at least one file each year since 1986.
>>
>> I
> > Yep, this is what we did for this year. I just want to go one step
> > further and just collapse all years into one single range, based on
> > the fact that I have verified that we have made significant changes
> > to at least one file each year since 1986.
>
> I have already done this for som
I just want to go one step
further and just collapse all years into one single range, based on
the fact that I have verified that we have made significant changes
to at least one file each year since 1986.
Based on my conversations with rms about this, I feel safe to say that
that
Joel Brobecker writes:
>> Good news: the GCS has been updated to explain that using copyright
>> year ranges is now ok. The only conditions are that you perform
>>
>> https://savannah.gnu.org/forum/forum.php?forum_id=6576
>>
>> the strict conversion (i.e., "2002,2004" cannot be converted t
> Good news: the GCS has been updated to explain that using copyright
> year ranges is now ok. The only conditions are that you perform
>
> https://savannah.gnu.org/forum/forum.php?forum_id=6576
>
> the strict conversion (i.e., "2002,2004" cannot be converted to
> "2002-2004") and that you a
Joel Brobecker wrote:
> Hi Jim,
>
>> Currently parted work and an imminent coreutils release are taking all of
>> my time. Maybe Joel Denny can help? At worst, I'll follow up next week.
>
> This really has no urgency at all. I've done the update for GDB and
> we are good for another year.
>
> Al
Hi Jim,
> Currently parted work and an imminent coreutils release are taking all of
> my time. Maybe Joel Denny can help? At worst, I'll follow up next week.
This really has no urgency at all. I've done the update for GDB and
we are good for another year.
Also, I am trying to get the OK from t
Joel Brobecker wrote:
> Hello, and Happy New Year :-).
Hi Joel,
Happy new year to you, too.
Currently parted work and an imminent coreutils release are taking all of
my time. Maybe Joel Denny can help? At worst, I'll follow up next week.
> I am trying to use gnulib's update-
Hello, and Happy New Year :-).
I am trying to use gnulib's update-copyright script to update all
of GDB's files. It's working quite beautifully, and it's quite fast
too. I only have a couple of issues:
- C files: In GDB, the style for comments is to avoid the '*'
FYI,
>From fc9846f7408ed30a3421eff5450ff5287cd66ddd Mon Sep 17 00:00:00 2001
From: Jim Meyering
Date: Sun, 1 Jan 2012 10:00:41 +0100
Subject: [PATCH] version-etc: update copyright year reported by --version
* lib/version-etc.c (COPYRIGHT_YEAR): Update to 2012.
Copyright (C) 1997-2012 F
Jim Meyering wrote:
> It looks like somehow perl is being run with -pi.bak.
Yes, apparently this is the cause. The .bak suffix appears to be the default.
I have not specified it through environment variables.
$ ls -l foo3*
-rw-r--r-- 1 bruno Kein 73 Nov 25 21:46 foo3.c
$ perl -pi -e s/x/x/ foo3.
Simon Josefsson wrote:
> Jim Meyering writes:
>
>> Hi Simon,
>> It looks like somehow perl is being run with -pi.bak.
>>
>> However, here's a patch that should avoid that:
>
> Thank you! I'll re-enable the self-test in libidn and proceed with the
> release process...
Pushed.
>>> test-update-cop
Simon Josefsson writes:
> Jim Meyering writes:
>
>> Hi Simon,
>> It looks like somehow perl is being run with -pi.bak.
>>
>> However, here's a patch that should avoid that:
>
> Thank you! I'll re-enable the self-test in libidn and proceed with the
> release process...
I noticed the patch hasn'
Jim Meyering writes:
> Hi Simon,
> It looks like somehow perl is being run with -pi.bak.
>
> However, here's a patch that should avoid that:
Thank you! I'll re-enable the self-test in libidn and proceed with the
release process...
>> test-update-copyright.sh that creates them, so I suspect tha
Simon Josefsson wrote:
> This problem came up for Libidn but it seems to be a problem with the
> update-copyright self check, it fails under Cygwin.
>
>> * Cygwin 1.7.9
>>
>> Fails already in the gnulib tests:
>>
>> 1 of 36 tests failed
>>
>&g
This problem came up for Libidn but it seems to be a problem with the
update-copyright self check, it fails under Cygwin.
> * Cygwin 1.7.9
>
> Fails already in the gnulib tests:
>
> 1 of 36 tests failed
>
> --- - 2011-11-23 01:13:33.194375000 +0100
> +++ update-copyright.
Thanks, I'd forgotten about the more general mechanisms.
--
http://rrt.sc3d.org
On 04/29/2011 08:32 AM, Reuben Thomas wrote:
> Two small niggles:
>
> 1. No option to turn off updating to the current year. I do take care
> not to add years in which I don't change files (I know that this is
> fussy), and I was just using update-copyright to compress
Reuben Thomas wrote:
> Two small niggles:
>
> 1. No option to turn off updating to the current year. I do take care
> not to add years in which I don't change files (I know that this is
> fussy), and I was just using update-copyright to compress year ranges.
There is no long
Two small niggles:
1. No option to turn off updating to the current year. I do take care
not to add years in which I don't change files (I know that this is
fussy), and I was just using update-copyright to compress year ranges.
2. No way to exclude files that are under VC but not fro
In other words
Right. Thanks for reading my screed :).
+0.1 Basic Installation
Oops, thanks for noticing. It's a temporary bug in the development
makeinfo that I've been using. I'll regenerate to fix it, no need to
change anything in gnulib.
k
On 01/02/2011 04:58 PM, Karl Berry wrote:
>> BTW, is there some reason why install.texi makes the nonstandard
>> formatting setting:
>> @firstparagraphindent insert
>> Personally, I think it would be better to take the default, just because
>> it's the default, though I can't say I'm too worked up
Josefsson wrote:
>>>>>>> How about this patch? Not all projects are copyright'ed by the FSF.
>>>>>>> The patch makes it possible to override the otherwise hard-coded string,
>>>>>>> thought cfg.mk and without modifying the update-copyrigh
Not all projects are copyright'ed by the FSF.
>>>>>> The patch makes it possible to override the otherwise hard-coded string,
>>>>>> thought cfg.mk and without modifying the update-copyright script iself.
>>>>>
>>>>> I li
>>> The patch makes it possible to override the otherwise hard-coded string,
>>>>> thought cfg.mk and without modifying the update-copyright script iself.
>>>>
>>>> I like it.
>>>> One suggestion before you push it:
>>
>> Anot
It was added explicitly in Autoconf v2.62-95-g02fa53b for better
plaintext rendering, see:
http://lists.gnu.org/archive/html/autoconf-patches/2008-08/msg00132.html
http://lists.gnu.org/archive/html/bug-gnulib/2008-08/msg00239.html
Well, sigh. "better" here is an aesthetic opinion,
otherwise hard-coded string,
>>>> thought cfg.mk and without modifying the update-copyright script iself.
>>>
>>> I like it.
>>> One suggestion before you push it:
>
> Another suggestion :)
Fine with me. Ok to push, Jim? Bruce, feel free to push it
ught cfg.mk and without modifying the update-copyright script iself.
>>
>> I like it.
>> One suggestion before you push it:
Another suggestion :)
diff --git a/build-aux/update-copyright b/build-aux/update-copyright
index db59cc7..9961732 100755
--- a/build-aux/update-copyright
++
Jim Meyering writes:
> Simon Josefsson wrote:
>> How about this patch? Not all projects are copyright'ed by the FSF.
>> The patch makes it possible to override the otherwise hard-coded string,
>> thought cfg.mk and without modifying the update-copyright script i
Simon Josefsson wrote:
> How about this patch? Not all projects are copyright'ed by the FSF.
> The patch makes it possible to override the otherwise hard-coded string,
> thought cfg.mk and without modifying the update-copyright script iself.
I like it.
One suggestion before you pu
How about this patch? Not all projects are copyright'ed by the FSF.
The patch makes it possible to override the otherwise hard-coded string,
thought cfg.mk and without modifying the update-copyright script iself.
/Simon
diff --git a/ChangeLog b/ChangeLog
index 1ba0366..17115d4 100644
[ adding bug-autoconf, as install.texi is from Autoconf ]
Hi Karl, and a happy new year everyone!
* Karl Berry wrote on Sun, Jan 02, 2011 at 12:17:21AM CET:
> Thanks. Those are probably worth excluding manually.
> Let's hear what Karl has to say.
>
> Excluding INSTALL* and install.texi
Thanks. Those are probably worth excluding manually.
Let's hear what Karl has to say.
Excluding INSTALL* and install.texi from this process sounds good to me.
BTW, is there some reason why install.texi makes the nonstandard
formatting setting:
@firstparagraphindent insert
Personally, I t
Bruno Haible wrote:
> Hi Jim,
>
>> Here's the whole thing:
>
> Thanks for showing it. The hunks I've looked at look all fine.
Thanks for the review, Bruno.
I've made one more change to the update-copyright rule,
patch below, then pushed the change that results fr
Hi Jim,
> Here's the whole thing:
Thanks for showing it. The hunks I've looked at look all fine.
Bruno
Hi Jim,
> doc/INSTALL | 3 +--
> doc/INSTALL.ISO | 3 +--
> doc/INSTALL.UTF-8 | 3 +--
These are automatically generated from doc/install.texi. I think Karl would
need to update the
Without this patch, and with my left-over setting,
export UPDATE_COPYRIGHT_MAX_LINE_LENGTH=79
the update-copyright test would fail:
FAIL: test-update-copyright.sh (exit: 1)
--- - 2010-01-01 11:23:31.412799557 +0100
+++ update-copyright.test-ex.1 2010-01-01 11:23:31.400435448 +0100
we decide something different...
>>
>> > ...
>> >> grep -l -w Copyright $$($(VC_LIST_EXCEPT)) \
>> >> - | grep -v -E '$(update-copyright-exclude-regexp)' \
>> >> + $(srcdir)/ChangeLog | grep -v COPYING
> > ...
> >>grep -l -w Copyright $$($(VC_LIST_EXCEPT)) \
> >> -| grep -v -E '$(update-copyright-exclude-regexp)' \
> >> + $(srcdir)/ChangeLog | grep -v COPYING \
> >> | $(update-copyright-env) xargs $(build_aux)/$@
> usual #!/usr/bin/perl first line,
Not exactly on topic, but FWIW I recommend #!/usr/bin/env perl.
That does not assume any particular Perl location.
Personally I find that preferable to Perl checking in configure scripts,
since then the resulting has a better chance of working on more syste
Eric Blake wrote:
> According to Jim Meyering on 8/15/2009 9:50 AM:
>>> I'm not sure why some invocations work and others fail, but the point is
>>> that update-copyright doesn't work as-is on cygwin 1.5; and it also has
>>> the annoying failure path
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 8/15/2009 9:50 AM:
>> I'm not sure why some invocations work and others fail, but the point is
>> that update-copyright doesn't work as-is on cygwin 1.5; and it also has
>> the annoying failur
-pi -e 's/1/2/' f
> $ cat f
> 2
> $ cat > foo <<\EOF
> #!/usr/bin/perl -pi
> s/2/3/;
> EOF
> $ chmod +x foo
> $ ./foo f
> Can't do inplace edit on f: Permission denied.
> $ ls f*
> f.bak foo
> $ mv f.bak f
> $ perl ./foo f
> Can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 8/15/2009 4:53 AM:
>> For the record, I discovered this because 'perl -ei' fails on cygwin 1.5 [but
>> works in cygwin 1.7] because of older cygwin's inability to delete in-use
>> files:
>
> That should be easy to detect.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 8/15/2009 6:46 AM:
> Obviously not worth duplicating code.
> I was thinking about projects with active ChangeLog files in
> subdirectories, e.g. gcc, emacs, glibc (not rotated ones).
They can provide an empty
LIST_EXCEPT)) \
>>> - | grep -v -E '$(update-copyright-exclude-regexp)' \
>>> + $(srcdir)/ChangeLog | grep -v COPYING \
>>> | $(update-copyright-env) xargs $(build_aux)/$@
>>
>> Adding back in the t
Copyright $$($(VC_LIST_EXCEPT)) \
>> - | grep -v -E '$(update-copyright-exclude-regexp)' \
>> +$(srcdir)/ChangeLog | grep -v COPYING \
>>| $(update-copyright-env) xargs $(build_aux)/$@
>
> Adding back in the top level ChangeLog
Eric Blake wrote:
> Eric Blake byu.net> writes:
>> I just noticed a problem. update-copyright is a perl script only intended
> for
>> maintainer use
>
> And we ought to support some form of 'build-aux/update-copyright --help' (and
> also --version), p
Eric Blake wrote:
> I just noticed a problem. update-copyright is a perl script only intended for
> maintainer use, which is fine, since only maintainers are required to have
> perl
> installed (after all, we already know that maintainers have perl by virtue of
> the fact that t
d be exempting all forms of COPYING (such as COPYING.LIB).
>>> And
>>> the use of .x-update-copyright seems cleaner than trying to write a sane
>>> regexp
>>> replacement in update-copyright-exclude-regexp (after all, I just got that
>>> wrong i
nk we should be exempting all forms of COPYING (such as COPYING.LIB). And
>> the use of .x-update-copyright seems cleaner than trying to write a sane
>> regexp
>> replacement in update-copyright-exclude-regexp (after all, I just got that
>> wrong in autoconf[1]). Would
Eric Blake byu.net> writes:
>
> I just noticed a problem. update-copyright is a perl script only intended
for
> maintainer use
And we ought to support some form of 'build-aux/update-copyright --help' (and
also --version), per GNU Coding Standards, before shipping pac
I just noticed a problem. update-copyright is a perl script only intended for
maintainer use, which is fine, since only maintainers are required to have perl
installed (after all, we already know that maintainers have perl by virtue of
the fact that they are running autoconf). But, as
Eric Blake wrote:
> Jim Meyering meyering.net> writes:
>> +# If you have an additional project-specific rule,
>> +# define it in cfg.mk and set this variable to its name.
>> +update-copyright-local ?=
>> +
>> .PHONY: update-copyright
>> -update-copyright
Jim Meyering meyering.net> writes:
>
> +# If you have an additional project-specific rule,
> +# define it in cfg.mk and set this variable to its name.
> +update-copyright-local ?=
> +
> .PHONY: update-copyright
> -update-copyright:
> +update-copyright: $(update-copy
+Copyright (C) 1996, 2000, 2001, 2005, 2007, 2008-2009 Free Software
Perhaps update-copyright could detect the convention being used, to
placate Jim :). Failing that, pushing Jim's willful decision to
compress years into update-copyright seems like the wrong move to me :).
I've
In testing out the new update-copyright script on autoconf, I noticed the
following conversion:
-Copyright (C) 1996, 2000, 2001, 2005, 2007, 2008 Free Software
+Copyright (C) 1996, 2000, 2001, 2005, 2007, 2008-2009 Free Software
Foundation, Inc.
In my opinion, this looks ugly for its
Le 31 juil. 09 à 15:52, Joel E. Denny a écrit :
Hi Joel,
+# Format within margin.
+my $new_wrapped;
+my $text_margin = $margin - length($prefix);
+while (length($new))
+ {
+if (($new =~ s/^(.{1,$text_margin})(?: |$)//)
+|| ($
Joel E. Denny wrote:
...
> That works for me. Thanks, and thanks for reviewing and pushing all my
> other patches.
>
> I'm not sure where ties between modules and maint.mk should be documented,
> but the stale advice in update-copyright ought to updated. Here's a
> patch.
Good idea. Pushed.
9 09:25:05 +0200
> Subject: [PATCH] maint.mk: support update-copyright-local
>
> * top/maint.mk (update-copyright-local): Define place-holder.
> (update-copyright): Depend on $(update-copyright-local).
That works for me. Thanks, and thanks for reviewing and pushing all my
other pat
Joel E. Denny wrote:
> On Thu, 6 Aug 2009, Jim Meyering wrote:
>
>> Joel E. Denny wrote:
>> > For Bison, update-copyright is not enough. Our backend skeletons contain
>> > m4 macro invocations with lists of copyright years as arguments. I've a
>> &g
1 - 100 of 115 matches
Mail list logo
