From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
"linux-next@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: ARC Port's linux-next URL update
Date: Wed, 20 Feb 2013 10:32:27 +0530 [thread overview]
Message-ID: <512458E3.8050402@synopsys.com> (raw)
In-Reply-To: <20130220102147.dc301eef8d32f0a88d066794@canb.auug.org.au>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Stephen,
On Wednesday 20 February 2013 04:51 AM, Stephen Rothwell wrote:
> Hi Vineet,
>
> On Tue, 19 Feb 2013 23:41:02 +0530 Vineet Gupta <Vineet.Gupta1@synopsys.com> wrote:
>>
>> Can you please point ARC's next tree to following:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/vgupta/arc.git for-next
>
> Done.
Thanks !.
>
>> This is an exact copy of what I had in github (based off 3.8-rc5)
>
> Not just a copy, but you did the right thing and it is the same commits.
> Thanks.
Yeah, that was the idea so that a worst case github branch's (signed tag )pull
request matched what I had here.
>
>> I suppose a week's worth of cooking should be enough to send a pull request to
Linus.
>
> Well, you have not rebased it so just moving sites should not affect
> you. However, even what is there has only been in -next for 2 days, so
> maybe a couple of days wait wouldn't hurt.
Cool !
Thx,
- -Vineet
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQIcBAEBAgAGBQJRJFjVAAoJEGnX8d3iisJeBp8P/048F3PjD1EsX6jrhLbsCwvP
ng9xjd1WN0CrKFziVg7yIedo1DNUg5+Hb6rkkFLy+3YiKp8RJu0tN7bi9QbOxCM6
sMky3HmGRPrfAkNcQZJOKEI+wm4DEikwPSy1C437fR8STBjmdV1Z1YAlni8Nf4XK
ZQiPCFh2ytOZQXD9jqU7rKyADDvcQGtcznv9PqcX66WuNgvlIyrOsLK/TrjY9f5G
p/pLM2f4/WyANYrkMRqDeEPF+44jbMYLeQsNs9VfccfWxAFSh4ObfZINqCHPcubU
XB3yv1+T61yewIw9q2NHh3UK5yhwuAvwdZHJdYNqRvK1YhRib54UUOXaJEBLISzv
Sqv3lQ1wTTRku93pI6ut6rj24RcwEMza3SMY9lhekXEpGVEgqcgdbJoX2GUlBWlE
rQDEeYoaVwEJ0xFjOiAw62JAaIdkWD1ko/rljWjQK3R7NHTYsNxvOcsyRYs5bjk8
hQaaaK/zPcTWW3HjSYJa43kL5dC2q3GFDA+SB7up6hkTNzOXXjdi/sYkzvOvxh85
Ln/RXhFPc3jLzNwbDH++uilNvBHTE98aI5wcHDXQ/PNxT7ZnbZHfMowmLcbm8kAP
mP00s2NA245ayJ5UsqeFvb+YjoB9qtIiPJNAKwPLX21jeAgjMz1Wi1HDbJ0jBkID
8CIpvoeoDA3/eEYlZVek
=cfos
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-02-20 5:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 18:11 ARC Port's linux-next URL update Vineet Gupta
2013-02-19 23:21 ` Stephen Rothwell
2013-02-20 5:02 ` Vineet Gupta [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=512458E3.8050402@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.