From: Robert Richter <rric@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: Re: Please add my tree to linux-next
Date: Fri, 1 Nov 2013 00:44:16 +0100 [thread overview]
Message-ID: <20131031234416.GK7429@rric.localhost> (raw)
In-Reply-To: <20131101093516.95affe68161b2761ec5edee8@canb.auug.org.au>
On 01.11.13 09:35:16, Stephen Rothwell wrote:
> Hi Robert,
>
> On Thu, 31 Oct 2013 20:39:44 +0100 Robert Richter <rric@kernel.org> wrote:
> >
> > please add my tree to linux-next:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/rric/linux.git for-next
> >
> > Preferable after the oprofile tree.
> >
> > This is a more general tree with stuff not related to oprofile.
>
> It would be good to know what you intent to put into that tree. Since it
> is currently empty, I have not added it today - and since the merge
> window will open before I do another linux-next release (after today's),
> I will not add it until after v3.13-rc1 is released (unless you tell me
> it will contain urgent stuff like bug fixes for v3.13).
I added this tree for hosting patches unrelated to oprofile, currently
these are edac and perf patches. At the moment I am using my oprofile
tree for this. But to not confuse people I want to use a repo with a
more generic name for this purpose in future.
There should be patches in for a couple of hours already. And the
contents is the same as in oprofile/for-next that hosts the same for a
couple of days already. Anyway, since this is more a transition from
one tree to another I can also wait.
Thanks,
-Robert
next prev parent reply other threads:[~2013-10-31 23:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 19:39 Please add my tree to linux-next Robert Richter
2013-10-31 22:35 ` Stephen Rothwell
2013-10-31 23:44 ` Robert Richter [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-02 4:22 Cong Wang
2011-12-04 23:09 ` Stephen Rothwell
2011-12-05 5:40 ` Cong Wang
2011-12-05 6:12 ` Stephen Rothwell
2011-12-05 6:52 ` Cong Wang
2011-12-07 9:35 ` Cong Wang
2011-12-07 10:37 ` 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=20131031234416.GK7429@rric.localhost \
--to=rric@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 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).