public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: BK: scsi-misc cs inconsistencies?
Date: 14 Jul 2004 08:33:03 -0500	[thread overview]
Message-ID: <1089811987.2222.12.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.60.0407141209450.2892@poirot.grange>

On Wed, 2004-07-14 at 05:24, Guennadi Liakhovetski wrote:
> Hello
> 
> I've searched scsi-misc cs-entries on bk, and they don't seem to be quite 
> consistent:
> 
> Linux kernel tree Search results for "tmscsim" in ChangeSet comments

If you mean you searched through the bk commits list, then yes, this is
what you see since change sets can renumber as trees are combined.

James



  reply	other threads:[~2004-07-14 13:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-14 10:24 BK: scsi-misc cs inconsistencies? Guennadi Liakhovetski
2004-07-14 13:33 ` James Bottomley [this message]
2004-07-14 19:28   ` Guennadi Liakhovetski

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=1089811987.2222.12.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-scsi@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