From: Helge Deller <deller@gmx.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-parisc@vger.kernel.org,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [GIT PULL] parisc updates for v3.10
Date: Thu, 09 May 2013 22:31:04 +0200 [thread overview]
Message-ID: <518C0788.8060200@gmx.de> (raw)
In-Reply-To: <20130508113704.5ac23906e0e513b4a76d5b55@canb.auug.org.au>
Hi Stephen,
On 05/08/2013 03:37 AM, Stephen Rothwell wrote:
> On Wed, 8 May 2013 00:11:02 +0200 Helge Deller <deller@gmx.de> wrote:
>>
>> please pull the parisc architecture updates for v3.10 from:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git parisc-for-3.10
>
> Does this mean that the parisc tree I have in linux-next
> (git://git.kernel.org/pub/scm/linux/kernel/git/jejb/parisc-2.6.git#for-next)
> is defunct?
Not sure. It will be either James or me who will send pull requests...
Of course we will agree who of us will do that and from which tree.
So, would it hurt if you add a second parisc tree for linux-next?
I've just created a "for-next" branch in my git repository:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git#for-next
Helge
next prev parent reply other threads:[~2013-05-09 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-07 22:11 [GIT PULL] parisc updates for v3.10 Helge Deller
2013-05-08 1:37 ` Stephen Rothwell
2013-05-09 20:31 ` Helge Deller [this message]
2013-05-10 0:15 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2013-05-13 20:48 Helge Deller
2013-05-13 21:53 ` Rolf Eike Beer
2013-06-18 21:39 Helge Deller
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=518C0788.8060200@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@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