All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: target-devel <target-devel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	Roland Dreier <roland@purestorage.com>
Subject: Re: [GIT PULL] target: Updates for v3.2-rc1 (round one)
Date: Tue, 25 Oct 2011 02:51:02 -0700	[thread overview]
Message-ID: <1319536262.18871.14.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <CA+55aFzUtu5jVt6XcP+cqLWSK1u+zbuJuWCJU0OhW2XVavv3VA@mail.gmail.com>

On Tue, 2011-10-25 at 11:44 +0200, Linus Torvalds wrote:
> On Tue, Oct 25, 2011 at 11:29 AM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > Hmm. This is not what I get. It might be a git version issue or diff
> > algorithm one - although that's actually pretty unusual. Do you do
> > something odd/special?
> 
> Another question: you picked a very particular and odd place to start
> development. It's commit 65112dccf8a ("Merge
> git://git.samba.org/sfrench/cifs-2.6") which just *seems* to be some
> "random Linux tree kernel of the day". I'm not seeing why you picked
> that one.
> 
> This is not a deal-breaker, and *please* don't use this as an argument
> for rebasing (quite the opposite), but it's basically a note to ask
> you to just pick a better starting point next time. It's usually much
> better to start from an actual release (preferably a *real* release,
> like 3.0) than from a "random daily tree". Of course, using an -rc1
> release is usually a really bad idea also, but in the rough timeframe
> we're talking about (October 10 - two weeks ago - that's apparently
> when you started worrying about this next merge window) you could have
> at least picked something like -rc9 as the base.
> 
> So basically, I'm asking that people not rebase, but also spend a bit
> of time thinking about "where should I start development".
> 

Point understood.   I'll make sure to pick a tagged -rc release for the
target-pending.git base next time.

Thank you,

--nab

  reply	other threads:[~2011-10-25  9:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-25  9:00 [GIT PULL] target: Updates for v3.2-rc1 (round one) Nicholas A. Bellinger
2011-10-25  9:29 ` Linus Torvalds
2011-10-25  9:42   ` Christoph Hellwig
2011-10-25  9:45     ` Linus Torvalds
2011-10-25 10:07       ` Nicholas A. Bellinger
2011-10-25  9:44   ` Linus Torvalds
2011-10-25  9:51     ` Nicholas A. Bellinger [this message]
2011-10-25  9:45   ` Nicholas A. Bellinger
2011-10-25  9:48     ` Linus Torvalds
2011-10-25  9:48       ` Linus Torvalds
2011-10-25  9:56       ` Nicholas A. Bellinger

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=1319536262.18871.14.camel@haakon2.linux-iscsi.org \
    --to=nab@linux-iscsi.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=roland@purestorage.com \
    --cc=target-devel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.