From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfa] License clarification for observer.texi
Date: Wed, 10 May 2006 17:43:00 -0000 [thread overview]
Message-ID: <uslnh93o0.fsf@gnu.org> (raw)
In-Reply-To: <20060510035245.GA25470@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 9 May 2006 23:52:45 -0400)
> Date: Tue, 9 May 2006 23:52:45 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> On Wed, May 10, 2006 at 06:23:35AM +0300, Eli Zaretskii wrote:
> > > Date: Tue, 9 May 2006 16:34:43 -0400
> > > From: Daniel Jacobowitz <drow@false.org>
> > >
> > > Would you like me to add copyright and license notices to all the other
> > > files which go into the GDB manual, referring to gdb.texinfo for
> > > copying conditions?
> >
> > In general yes, but what other files are there?
>
> agentexpr.texi appears to be the only other one which lacks a copyright
> notice
You are right (I somehow thought we no longer include that in the
manual, but I was wrong). We do need to add the copyright notice to
it. I suggest to use the wording the Emacs distribution uses for
files @included by emacs.texi.
next prev parent reply other threads:[~2006-05-10 17:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 21:04 Daniel Jacobowitz
2006-05-08 21:24 ` Eli Zaretskii
2006-05-08 22:18 ` Daniel Jacobowitz
2006-05-09 3:32 ` Eli Zaretskii
2006-05-09 4:06 ` Daniel Jacobowitz
2006-05-09 18:57 ` Eli Zaretskii
2006-05-09 19:03 ` Daniel Jacobowitz
2006-05-09 19:29 ` Eli Zaretskii
2006-05-09 19:35 ` Daniel Jacobowitz
2006-05-09 12:59 ` Daniel Jacobowitz
2006-05-09 19:20 ` Eli Zaretskii
2006-05-09 19:27 ` Daniel Jacobowitz
2006-05-09 20:29 ` Eli Zaretskii
2006-05-09 20:34 ` Daniel Jacobowitz
2006-05-10 3:23 ` Eli Zaretskii
2006-05-10 3:52 ` Daniel Jacobowitz
2006-05-10 17:43 ` Eli Zaretskii [this message]
2006-05-09 20:50 ` Daniel Jacobowitz
2006-05-10 14:59 ` Daniel Jacobowitz
2006-05-10 18:10 ` Eli Zaretskii
2006-05-10 18:49 ` Daniel Jacobowitz
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=uslnh93o0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@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