* linux-next: comment on the kbuild tree
@ 2013-05-14 23:25 Stephen Rothwell
2013-05-15 12:25 ` Michal Marek
0 siblings, 1 reply; 2+ messages in thread
From: Stephen Rothwell @ 2013-05-14 23:25 UTC (permalink / raw)
To: Michal Marek; +Cc: linux-next, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 260 bytes --]
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.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: linux-next: comment on the kbuild tree
2013-05-14 23:25 linux-next: comment on the kbuild tree Stephen Rothwell
@ 2013-05-15 12:25 ` Michal Marek
0 siblings, 0 replies; 2+ messages in thread
From: Michal Marek @ 2013-05-15 12:25 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-05-15 12:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-05-14 23:25 linux-next: comment on the kbuild tree Stephen Rothwell
2013-05-15 12:25 ` Michal Marek
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox