From: Michal Marek <mmarek@suse.cz>
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 kbuild tree
Date: Wed, 15 May 2013 14:25:38 +0200 [thread overview]
Message-ID: <51937EC2.6050604@suse.cz> (raw)
In-Reply-To: <20130515092505.294f3a8865c77e8420d27491@canb.auug.org.au>
On 15.5.2013 01:25, Stephen Rothwell wrote:
> Hi Michal,
>
> Since the kbuild tree now consists only of merge commits (relative to
> v3.10-rc1), you might as well just reset it to v3.10-rc1 and have a nice
> clean tree to start from.
I thought I would newer rebase the for-next branch to allow people to
pull from it. But I can see that it looks much cleaner in the linux-next
tree if you can do a git log stable..master and see what is really in
linux-next. So I reset it to v3.10-rc1 now.
Michal
prev parent reply other threads:[~2013-05-15 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 23:25 linux-next: comment on the kbuild tree Stephen Rothwell
2013-05-15 12:25 ` Michal Marek [this message]
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=51937EC2.6050604@suse.cz \
--to=mmarek@suse.cz \
--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.