From: hermann pitton <hermann-pitton@arcor.de>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL for 2.6.36] V4L/DVB fixes
Date: Thu, 30 Sep 2010 05:50:39 +0200 [thread overview]
Message-ID: <1285818639.6459.19.camel@pc07.localdom.local> (raw)
In-Reply-To: <4CA3FF3B.50004@redhat.com>
Am Donnerstag, den 30.09.2010, 00:08 -0300 schrieb Mauro Carvalho
Chehab:
> Em 29-09-2010 22:04, hermann pitton escreveu:
> >
> > Linus,
> >
> > Am Montag, den 27.09.2010, 17:02 -0700 schrieb Linus Torvalds:
> >> On Mon, Sep 27, 2010 at 1:57 PM, Mauro Carvalho Chehab
> >> <mchehab@redhat.com> wrote:
> >>> The following changes since commit 32163f4b2cef28a5aab8b226ffecfc6379a53786:
> >>>
> >>> alpha: fix usp value in multithreaded coredumps (2010-09-25 14:38:13 -0700)
> >>>
> >>> are available in the git repository at:
> >>> ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6.git v4l_for_linus
> >>
> >> I get
> >>
> >> scripts/kconfig/conf --oldconfig arch/x86/Kconfig
> >> drivers/media/Kconfig:146: 'endif' in different file than 'if'
> >> drivers/media/IR/Kconfig:15: location of the 'if'
> >> drivers/Kconfig:114: unexpected 'endmenu' within if block
> >> drivers/Kconfig:1: missing end statement for this entry
> >> make[1]: *** [oldconfig] Error 1
> >> make: *** [oldconfig] Error 2
> >>
> >> with this. And it seems to be due to a totally broken commit at the
> >> very beginning of the series by a commit called "Kconfig fixes"
> >> (Hah!), that clearly has not been tested at all.
> >>
> >> The commit sequence was also done today, apparently immediately before
> >> sending me the pull request. Which sure as hell explains the "clearly
> >> not tested at all" situation.
> >>
> >> Don't do this. You are now officially on my shit-list for sending me
> >> total crap.
> >>
> >> How effing hard can it be to understand: you don't send me stuff that
> >> hasn't been tested. It needs to be in -next for SEVERAL DAYS, and you
> >> don't rebase it or take it from some random quilt series just before
> >> sending it to me.
> >>
> >> That's true _especially_ during the -rc series. But it's damn well
> >> true at any other time too.
> >>
> >> I'm angry. I expect at least some _minimal_ amount of competence from
> >> people I pull from. This was not it. Get your ^&#! act together!
> >>
> >> Linus
> >
> > you should not be such rude.
> >
> > You have never been in any hardware details on v4l and dvb.
> >
> > After Gerd Knorr did quit, out of reasons, you noticed there is some
> > noise on v4l and dvb, but you never had to fix much on your own in the
> > last eight years.
> >
> > Shouting around and blaming others always was enough ...
> >
> > I agree, a rc-1 should be at least compile tested.
> >
> > Any idea, why this goes away?
>
> Hermann,
>
> That's OK. I did crap. Linus is right. I'll send him the patches again
> after having the same tree branch being tested for a few days at linux-next,
> without any bad results.
>
> Cheers,
> Mauro.
Mauro,
hopefully, a few days on linux-next can replace all what we had in the
past, causing sometimes years of delay ...
What to say ?
OK, if you say we are fine with it now, it is up to you.
So, the whole mistake was, that Linus did not start kicking asses harder
earlier?
What a total crap!
Cheers,
Hermann
next prev parent reply other threads:[~2010-09-30 3:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 20:57 Mauro Carvalho Chehab
2010-09-28 0:02 ` Linus Torvalds
2010-09-28 0:36 ` Mauro Carvalho Chehab
2010-09-30 9:56 ` Brian Rogers
2010-09-30 1:04 ` hermann pitton
2010-09-30 3:08 ` Mauro Carvalho Chehab
2010-09-30 3:50 ` hermann pitton [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-12 18:14 Mauro Carvalho Chehab
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=1285818639.6459.19.camel@pc07.localdom.local \
--to=hermann-pitton@arcor.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®