From: storm@cua.dk (Kim F. Storm)
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Years in copyright notices
Date: 23 Jun 2004 11:58:42 +0200 [thread overview]
Message-ID: <m3oenatx2l.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <20040623082221.GA27982@fencepost>
Miles Bader <miles@gnu.org> writes:
> On Wed, Jun 23, 2004 at 10:08:41AM +0200, Kim F. Storm wrote:
> > A Miles pointed out, this will lead to some merge conflicts, but since
> > this is legal stuff, we have to accept that inconvenience.
>
> Richard's post indicated that we do _not_ have to `accept that
> inconvenience', that it isn't a critical point.
Right, but if we make an effort to bring this fully up-to-date,
I suggest that we can just as well use the proper format.
> Making sure the copyright notices include the appropriate years is reasonable
> -- and probably won't result in all that many problems because many files are
> already up-to-date -- but changing the date format is apparently not
> necessary (according to Richard's post), and will result in many more
> conflicts.
Still, it will only result in conflicts in the files where you actually
did update the copyright notice on the branch. If you didn't do that,
there will be no conflicts.
To me it doesn't make much sense to update the copyright on a "feature"
branch, as it is likely to conflict with updates on the trunk.
Some users have copyright-update in the save-buffer-hook, so maybe
copyright-update should query vc to know if it's working on a branch
and not do any update in that situation (or at least query the user).
Of course, we also have release branches for maintenance releases,
and we should update copyrights on those branches -- but then we
normally don't merge to/from such branches.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2004-06-23 9:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 5:08 Years in copyright notices Richard Stallman
2004-06-17 13:13 ` Kim F. Storm
2004-06-18 2:42 ` Miles Bader
2004-06-18 21:51 ` Richard Stallman
2004-06-21 20:46 ` Luc Teirlinck
2004-06-22 5:18 ` Eli Zaretskii
2004-06-22 23:17 ` Richard Stallman
2004-06-23 7:09 ` Jan D.
2004-06-24 23:48 ` Richard Stallman
2004-06-23 8:08 ` Kim F. Storm
2004-06-23 8:22 ` Miles Bader
2004-06-23 9:58 ` Kim F. Storm [this message]
2004-06-24 23:48 ` Richard Stallman
2004-06-25 0:03 ` Miles Bader
2004-06-23 22:39 ` Kevin Ryde
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=m3oenatx2l.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.