linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Subject: Re: for-4.15/block rebased
Date: Sat, 11 Nov 2017 01:07:51 -0800	[thread overview]
Message-ID: <20171111090751.GA13421@infradead.org> (raw)
In-Reply-To: <7217b2a1-12cb-966d-5dd8-0d290f8be695@kernel.dk>

Yikes.  Can you at least re-pull the nvme bits so we can keep
the original commit dates for those?  Those actually are a huge
part of the rebased commits, and that way we might not get Linus
shouting at us this merge window at least..

On Fri, Nov 10, 2017 at 08:02:00PM -0700, Jens Axboe wrote:
> Hi,
> 
> Just a heads up that due to a fuckup of mine, I have rebased the above
> mentioned branch. The code is the same, but the history was screwed up.
> Not great timing coming up on the merge window, but it is what it is...
> 
> -- 
> Jens Axboe
> 
---end quoted text---

  reply	other threads:[~2017-11-11  9:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-11  3:02 for-4.15/block rebased Jens Axboe
2017-11-11  9:07 ` Christoph Hellwig [this message]
2017-11-11 22:37   ` Jens Axboe

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=20171111090751.GA13421@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=linux-block@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).