From: Mike Frysinger <vapier@gentoo.org>
To: gdb@sourceware.org
Cc: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>,
Binutils <binutils@sourceware.org>,
Peter Bergner <bergner@vnet.ibm.com>,
Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>
Subject: Re: Vendor branches on sourceware.org's binutils-gdb repo
Date: Tue, 08 Apr 2014 23:17:00 -0000 [thread overview]
Message-ID: <5147380.qGS8As6KbI@vapier> (raw)
In-Reply-To: <53406399.9050303@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
On Sat 05 Apr 2014 17:12:09 Edjunior Barbosa Machado wrote:
> at the time when binutils/gdb was moving to git, there has been some
> discussion in the mailing list [1] about the possibility of hosting
> vendor branches on sourceware.org's binutils-gdb git repository but, as
> far as I understood, there has been no agreement about this policy.
>
> We already maintain community vendor branches for glibc (on
> sourceware.org) and gcc (on gnu.org), and we'd like to do the same for
> binutils-gdb. The idea is to create separate namespaces, i.e.
> ibm/gdb/7.7 and ibm/binutils/2.24. Those branches will only store
> patches under GPL and with a proper copyright assignment.
>
> Any comments? Objections?
i'd use it for Gentoo if it were available. i've gotten all the gdb changes
merged at this point (i just do random back ports), but binutils is another
story ...
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-04-08 23:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 20:12 Edjunior Barbosa Machado
2014-04-06 6:02 ` Sergio Durigan Junior
2014-04-06 19:18 ` Aaro Koskinen
2014-04-07 3:51 ` Joel Brobecker
2014-04-07 14:27 ` Michael Matz
2014-04-07 14:47 ` Joel Brobecker
2014-04-07 15:41 ` Markus Trippelsdorf
2014-04-07 14:52 ` Mark Kettenis
2014-04-07 15:06 ` Andreas Schwab
2014-04-07 15:16 ` Matthew Fortune
2014-04-07 15:39 ` Mark Kettenis
2014-04-07 15:43 ` Andreas Schwab
2014-04-07 15:44 ` Michael Matz
2014-04-07 15:41 ` Michael Matz
2014-04-07 15:46 ` Joel Brobecker
2014-04-07 15:48 ` Andreas Schwab
2014-04-09 1:49 ` Matt Rice
2014-04-09 12:46 ` Joel Brobecker
2014-04-08 23:17 ` Mike Frysinger [this message]
2014-04-09 17:58 ` Stan Shebs
2014-04-09 18:41 ` Doug Evans
2016-06-27 19:15 ` Mike Frysinger
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=5147380.qGS8As6KbI@vapier \
--to=vapier@gentoo.org \
--cc=bergner@vnet.ibm.com \
--cc=binutils@sourceware.org \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb@sourceware.org \
--cc=tuliom@linux.vnet.ibm.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