From: Richard Sandiford <richard.sandiford@arm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org, David Malcolm <dmalcolm@redhat.com>
Subject: Re: [committed] Update copyright years, part 2
Date: Tue, 13 Jan 2015 17:16:00 -0000 [thread overview]
Message-ID: <87y4p61ug4.fsf@e105548-lin.cambridge.arm.com> (raw)
In-Reply-To: <20150105123924.GR1667@tucnak.redhat.com> (Jakub Jelinek's message of "Mon, 5 Jan 2015 13:39:24 +0100")
Jakub Jelinek <jakub@redhat.com> writes:
> Patch too large to attach uncompressed, this
> has been created with update-copyright.py --this-year.
> Note, I had to temporarily move away gcc/jit/docs/conf.py,
> the python script dies on that and leaves almost all files unchanged.
Thanks for doing the update. Is the patch below OK to fix the JIT thing?
After this change, update-copyright.py --this-year seems to update
gcc/jit correctly (including the texinfo files).
Richard
contrib/
* update-copyright.py (Copyright.__init__): Add a regexp for
"copyright = u'".
(Copyright.update_copyright): Don't add a space before the year
in that case.
Index: contrib/update-copyright.py
===================================================================
--- contrib/update-copyright.py 2014-08-05 10:29:02.695491816 +0100
+++ contrib/update-copyright.py 2015-01-13 14:13:43.500812967 +0000
@@ -183,6 +183,7 @@ class Copyright:
'|[Cc]opyright\s+%s'
'|[Cc]opyright\s+©'
'|[Cc]opyright\s+@copyright{}'
+ '|copyright = u\''
'|@set\s+copyright[\w-]+)'
# 2: the years. Include the whitespace in the year, so that
@@ -363,7 +364,8 @@ class Copyright:
return (False, orig_line, next_line)
line = (line[:match.start (2)]
- + ' ' + canon_form + self.separator
+ + ('' if intro.startswith ('copyright = ') else ' ')
+ + canon_form + self.separator
+ line[match.end (2):])
# Use the standard (C) form.
next prev parent reply other threads:[~2015-01-13 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 12:39 Jakub Jelinek
2015-01-13 17:16 ` Richard Sandiford [this message]
2015-01-13 17:22 ` Jakub Jelinek
2015-01-15 22:42 ` Richard Sandiford
2016-01-04 14:30 Jakub Jelinek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y4p61ug4.fsf@e105548-lin.cambridge.arm.com \
--to=richard.sandiford@arm.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).