From: Sedat Dilek <sedat.dilek@googlemail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Christoph Hellwig <hch@lst.de>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Linus <torvalds@linux-foundation.org>,
Nick Piggin <npiggin@kernel.dk>
Subject: Re: linux-next: Tree for Nov 3
Date: Thu, 3 Nov 2011 08:29:06 +0100 [thread overview]
Message-ID: <CA+icZUX1juRU51gXFrX7ZeKgtV9=0bmFKLYZCcuyTfW5E1SL+A@mail.gmail.com> (raw)
In-Reply-To: <20111103172036.0795ce9559ab2dbfd5740a26@canb.auug.org.au>
On Thu, Nov 3, 2011 at 7:20 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> The linux-next tree on github is no longer being updated and will be
> removed soon.
>
> The patch is still absent from kernel.org.
>
> The summary at the end now has a "git -1 --oneline" appended to the lines
> indicating which tree is being merged. This was suggested by Mauro
> Chehab as an aid to maintainers so that they can easily tell which version
> of their tree was merged. Comments welcome.
>
> Changes since 20111102:
>
> Renamed trees:
> wireless -> wireless-next
> wireless-current -> wireless
>
Whuzzz up with VFS tree(s)?
[1] and [2] lists:
vfs git
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git#for-next
vfs-scale git
git://git.kernel.org/pub/scm/linux/kernel/git/npiggin/linux-npiggin.git#vfs-scale-working
Isn't vfs-scale [2] done?
I have so long not heard or read from Nick Piggin (vfs-scale), I hope
he is well.
Christoph take over as interim VFS stuff from Al (hope he is well,
too) and I have seen his and pending stuff from FS folk was merged
into Linus-tree.
Christoph, your for-next GIT branch [3] is dedicated for linux-next (v3.3)?
- Sedat -
[1] http://git.us.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=blob;f=Next/Trees#l89
[2] http://git.us.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=blob;f=Next/Trees#l90
[3] http://git.kernel.org/?p=linux/kernel/git/hch/vfs-queue.git;a=shortlog;h=refs/heads/for-next
next prev parent reply other threads:[~2011-11-03 7:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 6:20 linux-next: Tree for Nov 3 Stephen Rothwell
2011-11-03 7:29 ` Sedat Dilek [this message]
2011-11-03 11:41 ` Stephen Rothwell
2011-11-03 21:47 ` linux-next: Tree for Nov 3 (staging/et131x) Randy Dunlap
2011-11-04 10:27 ` Mark Einon
2011-11-04 15:53 ` Randy Dunlap
2011-11-04 17:58 ` [PATCH] linux-next: et131x: Fix build error when CONFIG_PM_SLEEP not enabled Mark Einon
2011-11-04 18:19 ` Randy Dunlap
2011-11-04 0:43 ` linux-next: Tree for Nov 3 (KVMTOOL_TEST_ENABLE) Randy Dunlap
2011-11-04 16:59 ` Randy Dunlap
2011-11-04 20:03 ` Pekka Enberg
2011-11-07 17:34 ` Randy Dunlap
2014-11-03 5:14 linux-next: Tree for Nov 3 Stephen Rothwell
2014-11-03 21:50 ` Guenter Roeck
2014-11-03 23:18 ` Stephen Rothwell
2015-11-03 3:47 Stephen Rothwell
2017-11-03 9:28 Stephen Rothwell
2017-11-03 21:03 Kees Cook
2020-11-03 7:19 Stephen Rothwell
2021-11-03 5:48 Stephen Rothwell
2022-11-03 5:21 Stephen Rothwell
2023-11-03 1:55 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='CA+icZUX1juRU51gXFrX7ZeKgtV9=0bmFKLYZCcuyTfW5E1SL+A@mail.gmail.com' \
--to=sedat.dilek@googlemail.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).