All of lore.kernel.org
 help / color / mirror / Atom feed
* Reporting Bugs on This List
@ 2010-03-23 19:05 Eduardo Panisset
  2010-03-23 19:22 ` Atis Elsts
  2010-03-23 19:27 ` David Miller
  0 siblings, 2 replies; 4+ messages in thread
From: Eduardo Panisset @ 2010-03-23 19:05 UTC (permalink / raw)
  To: netdev

Hi All,

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.
So I would like to know How would be the better way to report bugs on
this list ?

Thanks in advance,
Eduardo Panisset.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Reporting Bugs on This List
  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
  1 sibling, 0 replies; 4+ messages in thread
From: Atis Elsts @ 2010-03-23 19:22 UTC (permalink / raw)
  To: Eduardo Panisset; +Cc: netdev

You need to submit patches in a proper format, and with [PATCH] in
subject line, so they get tracked automatically.
Reading this may be helpful: http://www.kernel.org/pub/linux/docs/lkml/#s1-10
Patches to netdev also need to apply clearly to net-2.6 (right?) Linux
kernel tree.

Also, be prepared that it may take much more time than one day until
someone reviews them.

On Tue, Mar 23, 2010 at 9:05 PM, Eduardo Panisset
<eduardo.panisset@gmail.com> wrote:
> Hi All,
>
> 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.
> So I would like to know How would be the better way to report bugs on
> this list ?
>
> Thanks in advance,
> Eduardo Panisset.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


-- 
~Atis

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Reporting Bugs on This List
  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
  2010-03-23 20:06   ` Eduardo Panisset
  1 sibling, 1 reply; 4+ messages in thread
From: David Miller @ 2010-03-23 19:27 UTC (permalink / raw)
  To: eduardo.panisset; +Cc: netdev

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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Reporting Bugs on This List
  2010-03-23 19:27 ` David Miller
@ 2010-03-23 20:06   ` Eduardo Panisset
  0 siblings, 0 replies; 4+ messages in thread
From: Eduardo Panisset @ 2010-03-23 20:06 UTC (permalink / raw)
  To: David Miller; +Cc: netdev

Okay David,

Sorry, lack me experience on what to expect and what procedures I
should follow as is the first time I'm participating on this list.
However my intention is just to contribute for the kernel stability
and development.

I will be pacient.

Thanks.

Thank you also to Atis (I will check the link you have sent).

Eduardo Panisset.


On Tue, Mar 23, 2010 at 4:27 PM, David Miller <davem@davemloft.net> wrote:
> 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.
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2010-03-23 20:06 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2010-03-23 20:06   ` Eduardo Panisset

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.