public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Ali Akcaagac <aliakc@web.de>
Cc: Jamie Lenehan <lenehan@twibble.org>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [Dc395x] Re: [PATCH] dc395x - 1/3 remove-static-eeprom-struct
Date: 03 Aug 2003 12:31:38 -0500	[thread overview]
Message-ID: <1059932143.10853.112.camel@mulgrave> (raw)
In-Reply-To: <1059924971.5837.5.camel@localhost>

On Sun, 2003-08-03 at 10:36, Ali Akcaagac wrote:
> So if possible please add these 3 patches ontop of what's inside bk2,
> this will save us a lot of pain :)

That's not actually possible for me: the -bkX snapshots aren't tagged in
the main BK tree.  However, as long as no further updates are coming
from elsewhere, the tree head is usually "good enough" to apply patches
to.

In this case, it looks like with the exclusion I can apply to the tree
head, so I'll merge the scsi-misc-2.5 repository up there.

James




  reply	other threads:[~2003-08-03 17:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-03  8:27 [PATCH] dc395x - description Jamie Lenehan
2003-08-03  8:27 ` [PATCH] dc395x - 1/3 remove-static-eeprom-struct Jamie Lenehan
2003-08-03  8:28   ` [PATCH] dc395x - 2/3 remove-static-adapter-list Jamie Lenehan
2003-08-03  8:29     ` [PATCH] dc395x - 3/3 fix-failures Jamie Lenehan
2003-08-03 15:01   ` [PATCH] dc395x - 1/3 remove-static-eeprom-struct James Bottomley
2003-08-03 15:04     ` [Dc395x] " Ali Akcaagac
2003-08-03 15:13       ` James Bottomley
2003-08-03 15:36         ` Ali Akcaagac
2003-08-03 17:31           ` James Bottomley [this message]
2003-08-12  4:12             ` Ali Akcaagac
2003-08-12 10:29               ` Jamie Lenehan

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=1059932143.10853.112.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=aliakc@web.de \
    --cc=lenehan@twibble.org \
    --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