public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ali Akcaagac <aliakc@web.de>
To: James Bottomley <James.Bottomley@steeleye.com>
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: Tue, 12 Aug 2003 06:12:09 +0200	[thread overview]
Message-ID: <1060661529.2750.1.camel@localhost> (raw)
In-Reply-To: <1059932143.10853.112.camel@mulgrave>

On Sun, 2003-08-03 at 19:31, James Bottomley wrote:
> 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.

Can you now please include the 3 new patches in the test3 ? As long as
no one contributes other patches it's the chance to do it.

http://www.twibble.org/dist/dc395x/2.05/

01-03 should fit on bk3 w/o problems.


  reply	other threads:[~2003-08-12  4:12 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
2003-08-12  4:12             ` Ali Akcaagac [this message]
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=1060661529.2750.1.camel@localhost \
    --to=aliakc@web.de \
    --cc=James.Bottomley@steeleye.com \
    --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