From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] Question about patches
Date: Wed, 06 Feb 2013 09:40:29 +0100 [thread overview]
Message-ID: <511216FD.4020503@relinux.de> (raw)
In-Reply-To: <EE5E77B503DE9A478B63A89AAD2585EDB66A46@vpane.excalyptech.com>
Am 06.02.2013 01:05, schrieb Przemyslaw Wrzos:
>
> Hey Guys,
>
>
>
> Just a quick question about how the mailing list works. I submitted a
> patch a week ago for netsnmp but it hasn't got any replies. Is it
> appropriate to bump it with a follow up email until it gets noticed or
> is it in the pipeline somewhere eventually to get looked at? Is it
> better to start a discussion before submitting a patch instead?
>
Hi,
my experience is that it might take its time to get responses and often
enough the only response is Peter's commit message.
Right now there is a lot traffic on the list, so that I feinitely would
wait longer than one week, except there is a reason to want yout patch
in 2013.02.
Regards
Stephan
>
>
>
> Thanks for the insight,
>
> Przemyslaw Wrzos
>
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130206/daed273c/attachment.html>
next prev parent reply other threads:[~2013-02-06 8:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 0:05 [Buildroot] Question about patches Przemyslaw Wrzos
2013-02-06 8:40 ` Stephan Hoffmann [this message]
2013-02-06 22:37 ` Yann E. MORIN
2013-02-07 0:47 ` Przemyslaw Wrzos
2013-02-07 8:08 ` Daniel Nyström
2013-02-07 8:31 ` Thomas Petazzoni
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=511216FD.4020503@relinux.de \
--to=sho@relinux.de \
--cc=buildroot@busybox.net \
/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 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.