From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Ingo Molnar <mingo@elte•hu>
Cc: linux-next@vger•kernel.org
Subject: Re: linux-next: ftrace tree build failure
Date: Fri, 2 Jan 2009 21:22:42 +1100 [thread overview]
Message-ID: <20090102212242.13f9007e.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20090102091456.GB30018@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 1961 bytes --]
Hi Ingo,
On Fri, 2 Jan 2009 10:14:56 +0100 Ingo Molnar <mingo@elte•hu> wrote:
>
> this has been fixed already a few days ago (if you google for the build
> failure string it will send you straight to the fix patch) - i just didnt
> push it out to the -next branches yet during the hollidays. (did that now)
Thanks.
> Generally if you see a problem with our trees you can check whether an
> issue is still present in tip/master:
>
> http://people.redhat.com/mingo/tip.git/README
I'll try to remember ...
[I wish you had stopped there]
> before duplicating fixing effort and reporting it as a genuine issue -
It broke a linux-next build - just how genuine does an issue have to be?
Even if I knew you had already fixed it, I would still have reported it
(although saying where I got the fix from) so that others know why I have
had to apply a patch.
> especially in a busy timeframe like the merge window when the _next_ merge
> window is the least of our worries.
During the merge window, linux-next is not concerned with the _next_
merge window (as my previous reminder to people spelt out), but very much
with the current merge window. What you don't seem to realise is that
others use linux-next during the merge window to do integration testing
after fixing up their trees to cope with stuff that Linus has already
merged (in order - as much as possible - to not break Linus' tree). So
when you break the linux-next tree, you make life harder for them.
So, how much of your time would have been "wasted" remembering to put
that fix into the linux-next branch compared to my time and the time of
others?
And don't bother responding (especially privately) I don't need the
aggravation. If you feel a need to reply coming on, just delete this
email instead and pretend I didn't write it.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-02 10:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 9:07 linux-next: ftrace tree build failure Stephen Rothwell
2009-01-02 9:14 ` Ingo Molnar
2009-01-02 10:22 ` Stephen Rothwell [this message]
2009-01-02 11:16 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2009-01-07 0:53 Stephen Rothwell
2009-01-07 9:55 ` Ingo Molnar
2009-01-07 21:20 ` Stephen Rothwell
2008-11-25 3:21 Stephen Rothwell
2008-11-25 3:48 ` Steven Rostedt
2008-11-25 4:13 ` Stephen Rothwell
2008-11-25 4:31 ` Steven Rostedt
2008-11-25 5:09 ` Stephen Rothwell
2008-11-25 5:44 ` Steven Rostedt
2008-11-25 6:57 ` Stephen Rothwell
2008-11-25 7:14 ` Ingo Molnar
2008-11-25 7:26 ` Stephen Rothwell
2008-11-25 5:24 ` Steven Rostedt
2008-11-25 3:07 Stephen Rothwell
2008-11-25 3:21 ` Steven Rostedt
2008-11-25 7:28 ` Ingo Molnar
2008-11-25 7:43 ` Stephen Rothwell
2008-11-25 8:04 ` Ingo Molnar
2008-11-25 14:57 ` John W. Linville
2008-11-25 18:46 ` Luis R. Rodriguez
2008-11-26 0:08 ` Stephen Rothwell
2008-11-26 0:14 ` Luis R. Rodriguez
2008-08-25 3:08 Stephen Rothwell
2008-08-25 6:05 ` Ingo Molnar
2008-08-25 6:11 ` Ingo Molnar
2008-08-25 6:31 ` Stephen Rothwell
2008-08-25 3:01 Stephen Rothwell
2008-08-25 6:09 ` Ingo Molnar
2008-08-25 16:42 ` Steven Rostedt
2008-08-25 16:46 ` Steven Rostedt
2008-08-15 2:27 Stephen Rothwell
2008-08-15 7:56 ` Ingo Molnar
2008-08-15 8:29 ` Stephen Rothwell
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=20090102212242.13f9007e.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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