From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: trustees@gentoo.org
Subject: Re: [gentoo-project] Bad license and attribution by ChromiumOS and CoreOS
Date: Sat, 14 Mar 2015 01:29:07 +0300 [thread overview]
Message-ID: <20150314012907.572f174f9485c58cf5032a65@gentoo.org> (raw)
In-Reply-To: <CAGfcS_n2_j3G6an8WPZBPn76puYHYZuJgB_FjZB7FhNLXUZq=Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On Fri, 13 Mar 2015 18:17:12 -0400 Rich Freeman wrote:
> On Fri, Mar 13, 2015 at 7:26 AM, Rich Freeman <rich0@gentoo.org> wrote:
> > On Fri, Mar 13, 2015 at 6:30 AM, Andrew Savchenko <bircoph@gentoo.org> wrote:
> >> On Fri, 13 Mar 2015 00:41:11 -0400 Mike Frysinger wrote:
> >>> While we agree that the README can be misleading, that was certainly not the
> >>> point and has been updated:
> >>> https://chromium.googlesource.com/chromiumos/overlays/portage-stable/+/master/README
> >>
> >> Good. But github repo is still not fixed:
> >> https://github.com/coreos/portage-stable
> >>
> >
> > That is CoreOS, not ChromiumOS. We should ping them about this
> > separately. Since they're based on ChromiumOS I doubt they'll fuss
> > much over adopting the new README.
> >
> > I posted this on their -dev "list":
> > https://groups.google.com/forum/#!topic/coreos-dev/goLG-5r8m1s
> >
>
> ... and they have changed the file in question.
Great job. GPL prevails :)
I'm CCing trustees here, so they can see that issue is resolved.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-03-13 22:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 2:22 [gentoo-project] Bad license and attribution by ChromiumOS and CoreOS Patrick Lauer
2015-03-07 3:46 ` Alex Brandt
2015-03-07 3:55 ` Andrew Savchenko
2015-03-07 4:13 ` Rich Freeman
2015-03-07 13:44 ` Sven Vermeulen
2015-03-07 8:53 ` Ulrich Mueller
2015-03-07 9:05 ` Andrew Savchenko
2015-03-07 12:09 ` Rich Freeman
2015-03-07 14:27 ` Anthony G. Basile
2015-03-22 7:36 ` Jeroen Roovers
2015-03-22 8:21 ` Ulrich Mueller
2015-03-22 12:14 ` Rich Freeman
2015-03-22 16:22 ` Ulrich Mueller
2015-03-22 16:25 ` Mike Frysinger
2015-03-22 18:08 ` Ulrich Mueller
2015-03-11 6:11 ` Mike Frysinger
2015-03-07 9:33 ` Matthias Maier
2015-03-07 19:11 ` [gentoo-project] " Alec Warner
2015-03-11 5:22 ` Andrew Savchenko
2015-03-11 8:32 ` Kristian Fiskerstrand
2015-03-13 0:37 ` Alec Warner
2015-03-13 4:41 ` [gentoo-project] " Mike Frysinger
2015-03-13 7:46 ` Alexander Berntsen
2015-03-13 10:30 ` Andrew Savchenko
2015-03-13 11:26 ` Rich Freeman
2015-03-13 22:17 ` Rich Freeman
2015-03-13 22:29 ` Andrew Savchenko [this message]
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=20150314012907.572f174f9485c58cf5032a65@gentoo.org \
--to=bircoph@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=trustees@gentoo.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