From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: Copyright updates
Date: Thu, 04 Jan 2007 04:41:00 -0000 [thread overview]
Message-ID: <20070104044149.GA4414@nevyn.them.org> (raw)
In-Reply-To: <umz4z1kft.fsf@gnu.org>
On Thu, Jan 04, 2007 at 06:32:06AM +0200, Eli Zaretskii wrote:
> Why are we including a package in GDB that is part of Emacs, and
> why modify it while doing that? Can't we simply tell people ``use
> copyright.el from Emacs''?
Pragmatics: Because I needed to modify it to get the results I posted.
Otherwise, it has no respect for margins - it would just push things
further and further out to the right. And because the version in the
last release of emacs was too old to use, and the version in emacs CVS
needs to be modified to work with my system's installed emacs.
I'm happy to just check in the year updates and hold on to the script
if that's controversial (which I realize it may be, given the FSF
policy on importing modified files). It's probably possible to rewrite
my changes to use an installed CVS emacs and its copyright.el plus a
little extra goo, but I can't do it; my Lisp is too weak and I've spent
all the time on automating this that I can afford to. Same goes for
trying to get the copy in emacs CVS improved. Sorry :-( Another six
hours in the day...
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-01-04 4:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 1:16 Daniel Jacobowitz
2007-01-04 4:32 ` Eli Zaretskii
2007-01-04 4:41 ` Daniel Jacobowitz [this message]
2007-01-04 22:02 ` Eli Zaretskii
2007-01-04 22:09 ` Daniel Jacobowitz
2007-01-04 22:13 ` Eli Zaretskii
2007-01-06 14:05 ` Eli Zaretskii
2007-01-06 14:17 ` Eli Zaretskii
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=20070104044149.GA4414@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox