public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: "Randy Dunlap" <rdunlap-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Linus Torvalds
	<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [GIT PULL] i2c updates for 2.6.38
Date: Mon, 10 Jan 2011 14:58:00 -0800 (PST)	[thread overview]
Message-ID: <51321.148.87.67.136.1294700280.squirrel@xenotime.net> (raw)
In-Reply-To: <20110110233245.50d4efa2-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>


On Mon, January 10, 2011 2:32 pm, Jean Delvare wrote:
> On Mon, 10 Jan 2011 22:21:45 +0100, Jean Delvare wrote:
>
>> Please pull i2c subsystem updates for Linux 2.6.37 from:
>>
>
> Of course this should read: for Linux 2.6.38. Copy and paste is bad.


Replying to someone's own pull request for <earlier kernel version>
(with updated subject) is also bad.
Not that you are doing that, but a few people do.  :(

-- 
~Randy

  parent reply	other threads:[~2011-01-10 22:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 21:21 [GIT PULL] i2c updates for 2.6.38 Jean Delvare
     [not found] ` <20110110222145.31c40d8e-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-01-10 22:32   ` Jean Delvare
     [not found]     ` <20110110233245.50d4efa2-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-01-10 22:58       ` Randy Dunlap [this message]
2011-01-11 11:17   ` Mark Brown
     [not found]     ` <20110111111758.GH6541-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2011-01-11 11:25       ` Jean Delvare
2011-01-11 11:24         ` Mark Brown
     [not found]           ` <20110111112458.GA13429-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2011-01-13 21:22             ` Jean Delvare
     [not found]               ` <20110113222258.128d6a13-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2011-01-13 23:24                 ` Mark Brown

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=51321.148.87.67.136.1294700280.squirrel@xenotime.net \
    --to=rdunlap-/uha2rfvqtnk1umjsbkqmq@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.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