From: Michael Buesch <mb@bu3sch.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
bcm43xx-dev@lists.berlios.de
Subject: Re: b43: acking patches
Date: Sun, 3 Jan 2010 23:07:55 +0100 [thread overview]
Message-ID: <201001032307.57327.mb@bu3sch.de> (raw)
In-Reply-To: <b170af451001031330i514d3d8frcd3b29f697e42872@mail.gmail.com>
On Sunday 03 January 2010 22:30:27 Rafał Miłecki wrote:
> Michael, you gave me some reviews of patches I was very glad to see. I
> posted some (hopefully) corrected versions but didn't get your
> response.
>
> Can we expect you ACKing patches as well?
>
> I post this question publicly as I may be not the only one person who
> would like to know this.
Well, no response means I'm OK with it (or that I don't care).
In the past I used to ack all patches, but we changed that and I only
reply if I see problems with patches.
I usually respond within less than a day, if there's something I disagree with.
--
Greetings, Michael.
prev parent reply other threads:[~2010-01-03 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-03 21:30 b43: acking patches Rafał Miłecki
2010-01-03 22:07 ` Michael Buesch [this message]
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=201001032307.57327.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=zajec5@gmail.com \
/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.