From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] lis3lv02d: support both one- and two-byte sensors
Date: Wed, 11 Feb 2009 12:22:41 +0100 [thread overview]
Message-ID: <gmuce1$i20$1@ger.gmane.org> (raw)
In-Reply-To: 4992B393.8070808@drmicha.warpmail.net
On Wednesday 11 February 2009 12:16, Michael J Gruber wrote:
> Giuseppe,
>
> you may prefer sending this to the kernel mailing list rather than the
> git list. But we can tell you the patch is formatted as a proper git
> patch ;)
I know, I'm terribly sorry for the spamming I did. Fingers automatically went
for 'git@vger' instead of 'linux-kernel@vger' ... I'm so much more used to
sending patches to this list that it goes on automatically 8-/
I'll try not to repeat the mistake in the future 8-)
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2009-02-11 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 0:01 [PATCH] lis3lv02d: support both one- and two-byte sensors Giuseppe Bilotta
2009-02-11 11:16 ` Michael J Gruber
2009-02-11 11:22 ` Giuseppe Bilotta [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-10 23:34 Giuseppe Bilotta
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='gmuce1$i20$1@ger.gmane.org' \
--to=giuseppe.bilotta@gmail.com \
--cc=git@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).