From: Philippe Loctaux <phil@philippeloctaux.com>
To: sqawesome99@gmail.com
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Btrfs: async: fixed a brace coding style issue
Date: Sun, 21 Feb 2016 22:52:37 +0100 [thread overview]
Message-ID: <20160221215237.GA431@carbon.home> (raw)
On Sun, Feb 21, 2016 at 03:08:02PM -0600, Simon Quigley wrote:
> I thought I proposed this exact patch...hmm...
Yes you're right, I wasn't subscribed at the mailing list yet.
The maintainer will probably see it's a duplicate and he'll just ignore
that patch.
--
Philippe Loctaux
phil@philippeloctaux.com
next reply other threads:[~2016-02-21 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-21 21:52 Philippe Loctaux [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-21 20:50 [PATCH] Btrfs: async: fixed a brace coding style issue Philippe Loctaux
2016-02-21 21:08 ` Simon Quigley
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=20160221215237.GA431@carbon.home \
--to=phil@philippeloctaux.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sqawesome99@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.