From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: brobecker@adacore.com
Cc: gdb@sourceware.org
Subject: Re: GDB transition to GPLv3 should now be complete
Date: Fri, 24 Aug 2007 15:28:00 -0000 [thread overview]
Message-ID: <200708241528.l7OFSgDi030135@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <20070824151251.GG6056@adacore.com> (message from Joel Brobecker on Fri, 24 Aug 2007 11:12:51 -0400)
> Date: Fri, 24 Aug 2007 11:12:51 -0400
> From: Joel Brobecker <brobecker@adacore.com>
>
> GDB is now licensed under the terms of GPLv3.
>
> There is one issue identified left before the release: printing of
> signed and unsigned characters and strings. I found the patch
> submission, but it looks like it never went in (for lack of agreement
> on it?).
Yes, and I think the only reasonable thing to do in this case is to
stick with historical behaviour.
> I would like to give a week to any dust that might have been created by
> the switch to GPLv3 to settle. Let's take a decision about the issue
> above (either fix, defer, or leave as is). I'm targetting a branch
> creation date around Aug 31st (I'm actually flying again the next day,
> so the actual creation might happen a few days after).
Good! I'll try to give it a spin on several of my OpenBSD boxes.
Hopefully people will be a bit conservative with checking stuff in
before the branch is created.
Mark
next prev parent reply other threads:[~2007-08-24 15:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 15:08 Joel Brobecker
2007-08-24 15:28 ` Mark Kettenis [this message]
2007-08-24 15:33 ` Daniel Jacobowitz
2007-08-24 16:16 ` Mark Kettenis
2007-08-24 16:54 ` Daniel Jacobowitz
2007-08-24 18:11 ` Mark Kettenis
2007-08-24 18:40 ` Daniel Jacobowitz
2007-08-24 22:17 ` Daniel Jacobowitz
2007-08-25 9:36 ` Eli Zaretskii
2007-08-25 13:39 ` 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=200708241528.l7OFSgDi030135@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=brobecker@adacore.com \
--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