All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: comment on the xen-two tree
Date: Mon, 13 May 2013 09:48:18 -0400	[thread overview]
Message-ID: <20130513134818.GN6811@phenom.dumpdata.com> (raw)
In-Reply-To: <20130513095244.60176cad5e302c1156788096@canb.auug.org.au>

On Mon, May 13, 2013 at 09:52:44AM +1000, Stephen Rothwell wrote:
> Hi Konrad,
> 
> Since the xen-two tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> linux-next) seems to only consist of merges commits and some old (pre
> v3.9) stuff, it might be a good time to reset it to be just v3.10-rc1 (or
> rebase onto that) so you can start with a nice clean tree again.

Done!

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

  reply	other threads:[~2013-05-13 13:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-12 23:52 linux-next: comment on the xen-two tree Stephen Rothwell
2013-05-13 13:48 ` Konrad Rzeszutek Wilk [this message]
2013-05-14  0:08   ` Stephen Rothwell

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=20130513134818.GN6811@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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.