From: khc@pm.waw.pl (Krzysztof Halasa)
To: linux-arm-kernel@lists.infradead.org
Subject: Another tree for "next"
Date: Tue, 18 Sep 2012 12:32:38 +0200 [thread overview]
Message-ID: <m3ehlzmxix.fsf@intrepid.localdomain> (raw)
In-Reply-To: <20120911092614.d42403c55b516ea898fb5e21@canb.auug.org.au> (Stephen Rothwell's message of "Tue, 11 Sep 2012 09:26:14 +1000")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
>> >>> git://git.kernel.org/pub/scm/linux/kernel/git/chris/linux.git branch: next
> OK, I have added your tree from today.
Thanks a lot.
--
Krzysztof Halasa
prev parent reply other threads:[~2012-09-18 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3obli3j7a.fsf@intrepid.localdomain>
[not found] ` <20120910100144.dcbe2715cde0fea51345a354@canb.auug.org.au>
[not found] ` <m31ui9g4ff.fsf@intrepid.localdomain>
2012-09-10 17:52 ` Another tree for "next" Stephen Warren
2012-09-10 23:26 ` Stephen Rothwell
2012-09-18 10:32 ` Krzysztof Halasa [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=m3ehlzmxix.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=linux-arm-kernel@lists.infradead.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