From: Joel Brobecker <brobecker@adacore.com>
To: Michael Matz <matz@suse.de>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>,
aaro.koskinen@iki.fi, sergiodj@redhat.com,
emachado@linux.vnet.ibm.com, gdb@sourceware.org,
binutils@sourceware.org, bergner@vnet.ibm.com,
tuliom@linux.vnet.ibm.com
Subject: Re: Vendor branches on sourceware.org's binutils-gdb repo
Date: Mon, 07 Apr 2014 15:46:00 -0000 [thread overview]
Message-ID: <20140407154619.GJ4186@adacore.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1404071701320.23408@wotan.suse.de>
> It's not the infrastructure. It's policies. Some companies have a policy
> of not publishing any code outside except through a heavy process, which
> might include a white-list of where it may be published/hosted.
> sourceware.org is on that white-list already. It may be very painful to
> extend that white-list.
Companies that do have such a white list are an acceptable exception,
IMO, and I would be OK with having their branches in our sourceware.org
repository.
--
Joel
next prev parent reply other threads:[~2014-04-07 15:46 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 [this message]
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
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=20140407154619.GJ4186@adacore.com \
--to=brobecker@adacore.com \
--cc=aaro.koskinen@iki.fi \
--cc=bergner@vnet.ibm.com \
--cc=binutils@sourceware.org \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
--cc=matz@suse.de \
--cc=sergiodj@redhat.com \
--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