netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: eduardo.panisset@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: Reporting Bugs on This List
Date: Tue, 23 Mar 2010 12:27:47 -0700 (PDT)	[thread overview]
Message-ID: <20100323.122747.172618601.davem@davemloft.net> (raw)
In-Reply-To: <b7b22e81003231205v38fa8774y81da6da5278c99a2@mail.gmail.com>

From: Eduardo Panisset <eduardo.panisset@gmail.com>
Date: Tue, 23 Mar 2010 16:05:59 -0300

> I have already reported two bugs on XFRM framework since yesterday.
> However my reports haven't been answered yet (I thought strange as
> this list is very active) and one of my questions simply disappeared
> even if its a simple plain text messages without offensive terms
> neither I think any other constraint.

It's incredibly unreasonable to expect immediate responses from a
group of volunteers.

Personally, it takes me over 2 hours just to make a first pass over
the day's emails in the morning.  This means not even replying to
anything or reading any content seriously.  That's just deleting the
excess postings I have no direct interest in.

Then I go over patches, that can take 3 hours or more.

And then, and only then, can I look at bug reports and other things
which are not new patches.  And your mail falls into that category
because you didn't post a proper patch, and if you did you'd need
to properly signoff on the patch and provide a properly formed
commit message.

You just need to be patient.

  parent reply	other threads:[~2010-03-23 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23 19:05 Reporting Bugs on This List Eduardo Panisset
2010-03-23 19:22 ` Atis Elsts
2010-03-23 19:27 ` David Miller [this message]
2010-03-23 20:06   ` Eduardo Panisset

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=20100323.122747.172618601.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=eduardo.panisset@gmail.com \
    --cc=netdev@vger.kernel.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).