From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Stephane Grosjean <s.grosjean@peak-system.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Oliver Hartkopp <socketcan@hartkopp.net>
Subject: Re: [PATCH v4] can/peak_usb: add support for PEAK new CANFD USB adapters
Date: Wed, 14 Jan 2015 12:07:11 +0100 [thread overview]
Message-ID: <54B64DDF.5050909@pengutronix.de> (raw)
In-Reply-To: <54B64B41.2040500@peak-system.com>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
On 01/14/2015 11:56 AM, Stephane Grosjean wrote:
> Hi again Marc,
>
> Well... What's wrong?
>
> $ git clone https://gitorious.org/linux-can/linux-can.git
> Cloning into 'linux-can'...
> error: RPC failed; result=22, HTTP code = 504
> fatal: The remote end hung up unexpectedly
>
> (same with linux-can-next...)
Same here:
> ➜ (pts/32) frogger@hardanger:/tmp git clone https://gitorious.org/linux-can/linux-can.git
> Cloning into 'linux-can'...
> error: RPC failed; result=22, HTTP code = 504
> fatal: The remote end hung up unexpectedly
504 is Gateway timeout - maybe the kernel is too big to clone :D
I'd suggest to add can and can-next as a remote to an existing linux git tree.
Skip the first step if you already have a linux git tree:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
cd linux
git remote add -f can https://gitorious.org/linux-can/linux-can.git
git remote add -f can-next https://gitorious.org/linux-can/linux-can-next.git
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-01-14 11:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 10:00 [PATCH v4] can/peak_usb: add support for PEAK new CANFD USB adapters Stephane Grosjean
2015-01-07 17:03 ` Marc Kleine-Budde
2015-01-07 17:37 ` Oliver Hartkopp
2015-01-07 18:37 ` iproute2 fd-non-iso PoC - was " Oliver Hartkopp
2015-01-08 9:04 ` Marc Kleine-Budde
2015-01-08 9:09 ` Marc Kleine-Budde
2015-01-13 13:18 ` Stephane Grosjean
2015-01-13 13:29 ` Marc Kleine-Budde
2015-01-13 13:32 ` Marc Kleine-Budde
2015-01-14 10:50 ` Stephane Grosjean
2015-01-14 10:51 ` Marc Kleine-Budde
2015-01-14 10:56 ` Stephane Grosjean
2015-01-14 11:07 ` Marc Kleine-Budde [this message]
2015-01-14 18:55 ` Oliver Hartkopp
2015-01-14 20:57 ` Marc Kleine-Budde
2015-01-15 15:49 ` Marc Kleine-Budde
2015-01-14 12:05 ` Fwd: " Stephane Grosjean
2015-01-14 13:00 ` Andri Yngvason
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=54B64DDF.5050909@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=s.grosjean@peak-system.com \
--cc=socketcan@hartkopp.net \
/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).