Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Paul Moore <paul.moore@hp.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: linux-next: rebase of lblnet tree
Date: Thu, 11 Jul 2013 10:01:17 +1000	[thread overview]
Message-ID: <20130711100117.8b042a1a2a494bb9ee0003fd@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 444 bytes --]

Hi Paul,

Why have you just rebased the lblnet tree
(git://git.infradead.org/users/pcmoore/lblnet-2.6_next#master)?  You have
just invalidated your testing and made it likely that Linus will blast
you if you ask him to pull your tree.  Your whole tree was already based
after v3.10 (i.e. released or rebased after the merge window opened), so
why move it again?

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2013-07-11  0:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11  0:01 Stephen Rothwell [this message]
2013-07-11  3:09 ` linux-next: rebase of lblnet tree Paul Moore

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=20130711100117.8b042a1a2a494bb9ee0003fd@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paul.moore@hp.com \
    /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