From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>, gdb@sourceware.org
Subject: Re: Documentation generated from sources proposal
Date: Mon, 12 Oct 2009 18:07:00 -0000 [thread overview]
Message-ID: <20091012180704.GA7228@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <20091012180027.GA2107@caradoc.them.org>
On Mon, 12 Oct 2009 20:00:27 +0200, Daniel Jacobowitz wrote:
> On Mon, Oct 12, 2009 at 07:15:56PM +0200, Jan Kratochvil wrote:
> > Still GDB can already start using new gdbint-type documentation parts in the
> > sources instead of writing it in gdbint.texinfo and obsoleting the parts in
> > gdbint.texinfo, just one cannot move updated parts.
>
> Not without changing the license of the GDB Internals manual.
This is still misunderstood.
I can write a completely new comment in gdb/breakpoint.c in the gtk-doc
format. This new comment is unrelated to the license of gdbint.texinfo.
Still such possibility would not be enough for my current patch so it will
probably still remain unresolved for some time.
Regards,
Jan
next prev parent reply other threads:[~2009-10-12 18:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 16:14 Jan Kratochvil
2009-10-12 17:12 ` Tom Tromey
2009-10-12 17:16 ` Jan Kratochvil
2009-10-12 18:00 ` Daniel Jacobowitz
2009-10-12 18:07 ` Jan Kratochvil [this message]
2009-10-12 18:13 ` Daniel Jacobowitz
2009-10-12 18:20 ` Jan Kratochvil
2009-10-12 18:26 ` Tom Tromey
2009-10-12 18:30 ` Jan Kratochvil
2009-10-12 18:54 ` Eli Zaretskii
2009-10-12 19:10 ` Daniel Jacobowitz
2009-10-12 19:25 ` Tom Tromey
2009-10-12 20:23 ` Eli Zaretskii
2009-10-12 18:57 ` Eli Zaretskii
2009-10-13 8:23 ` Jeremy Bennett
2009-10-13 18:16 ` Eli Zaretskii
2009-10-13 19:13 ` Jan Kratochvil
2009-10-13 19:18 ` Eli Zaretskii
2009-10-27 10:07 ` Mark Kettenis
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=20091012180704.GA7228@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=tromey@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