From: "Carlos O'Donell" <carlos@redhat.com>
To: munroesj@linux.vnet.ibm.com
Cc: Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] Add hwcap2 bits for POWER9
Date: Tue, 12 Jan 2016 12:45:37 -0500 [thread overview]
Message-ID: <56953BC1.7050705@redhat.com> (raw)
In-Reply-To: <1452616757.29488.10.camel@oc7878010663>
On 01/12/2016 11:39 AM, Steven Munroe wrote:
>> That's the rule. There are no other discussions to be had.
>>
> Well is was posted to to powerpc next:
> https://git.kernel.org/powerpc/c/e708c24cd01ce80b1609d8bacc
>
> We have agreement between the kernel and GLIBC (and the ABI).
>
> The issue is just coordination across communities and individuals that
> may not being paying attention to other communities dead lines.
>
> Have you ever tried to push a string, up hill. That is open source
> development in nutshell. ;)
I know exactly what this is like.
> So it is in flight and glibc is soft/slush freeze. I would hate to
> revert this one day just to add it back to the next. Especially if those
> days straddle the hard freeze ...
>
> So can we let this ride a day or too?
Sure. I'm not an unreasonable person.
My goal as a glibc steward is to remind IBM that our best practice is that
we *wait* until it goes into mainline before committing to glibc master.
There really isn't any reason to check this in to glibc master right now.
It could wait.
Adhemerval as a release manager is also not an unreasonable person.
I have already discussed with Tulio that he should have just waited to
commit these changes, but gotten an exception from Adhemerval to checkin
the fairly low-risk patches late in the freeze. That's exactly the purpose
of a release managers job, to grant you exceptions as we approach release,
particularly when schedules don't quite line up.
Cheers,
Carlos.
next prev parent reply other threads:[~2016-01-12 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <568C272D.6000705@linux.vnet.ibm.com>
[not found] ` <87egdsi4om.fsf@totoro.br.ibm.com>
[not found] ` <1452267366.5201.12.camel@vnet.ibm.com>
[not found] ` <568FE3D0.7080008@linaro.org>
2016-01-11 15:16 ` [PATCH] Add hwcap2 bits for POWER9 Tulio Magno Quites Machado Filho
2016-01-11 15:21 ` Carlos O'Donell
2016-01-11 19:55 ` Tulio Magno Quites Machado Filho
2016-01-11 20:48 ` Carlos O'Donell
2016-01-12 16:39 ` Steven Munroe
2016-01-12 17:45 ` Carlos O'Donell [this message]
2016-01-15 23:09 ` Michael Ellerman
2016-01-15 22:30 ` Carlos Eduardo Seo
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=56953BC1.7050705@redhat.com \
--to=carlos@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=munroesj@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.