linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: George Spelvin <linux@horizon.com>
Cc: pablo@netfilter.org, gaofeng@cn.fujitsu.com, kaber@trash.net,
	linux-kernel@vger.kernel.org, netfilter-devel@vger.kernel.org,
	netfilter@vger.kernel.org
Subject: Re: v3.10-rc7 oops soon after boot
Date: Tue, 25 Jun 2013 00:34:01 +0200	[thread overview]
Message-ID: <20130624223401.GC24827@pd.tnic> (raw)
In-Reply-To: <20130624221708.15489.qmail@science.horizon.com>

On Mon, Jun 24, 2013 at 06:17:08PM -0400, George Spelvin wrote:
> >> Reported-by: Borislav Petkov <bp@alien8.de>
> 
> > This should be:
> >
> > Reported-by: George Spelvin <linux@horizon.com>
> >
> > I only connected the dots...
> 
> Well, you did a whole lot more than me!  I just lobbed a "d'oh, it
> crashes" into the seething ocean of lkml.  (Admittedly, I had reason
> to act fast: we're very close to release.)
> 
> You figured out what subsystem was at fault and got the right people
> involved.  Definitely a valuable contribution.
> 
> Me, personally, I don't give a flying f*** about such credit; I had
> an itch and was trolling for someone to scratch it.
> 
> So feel free to take Reported-by (you are the one who reported it *to
> someone who could fix it*), Triaged-by, or whatever.

I was basically correcting how Reported-by is used - for the bug
reporter.

And yes, it is very important for us (even if you specifically don't
give a rat's rear end :-)) to credit the people - with their permission,
of course - who report bugs. Btw, I assume it is obvious why we need all
those good bug reports...

So I'm perfectly fine with you not giving flying f*ck about crediting as
long as you keep testing -rcs and reporting issues.

:-)

Thanks!

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-06-24 22:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24  6:49 v3.10-rc7 oops soon after boot George Spelvin
2013-06-24  7:03 ` George Spelvin
2013-06-24  7:33 ` Borislav Petkov
2013-06-24  8:47   ` George Spelvin
2013-06-24  9:12     ` Gao feng
2013-06-24  9:41       ` George Spelvin
2013-06-24  9:52         ` Gao feng
2013-06-24 10:01           ` George Spelvin
2013-06-24 11:34           ` Pablo Neira Ayuso
2013-06-24 15:10             ` Pablo Neira Ayuso
2013-06-24 16:13               ` Borislav Petkov
2013-06-24 22:17                 ` George Spelvin
2013-06-24 22:34                   ` Borislav Petkov [this message]
2013-06-25  1:36                   ` Gao feng
2013-06-25  6:17             ` Gao feng
2013-06-26  6:28             ` George Spelvin

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=20130624223401.GC24827@pd.tnic \
    --to=bp@alien8.de \
    --cc=gaofeng@cn.fujitsu.com \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=netfilter@vger.kernel.org \
    --cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).