From: David Miller <davem@davemloft.net>
To: mkl@pengutronix.de
Cc: netdev@vger.kernel.org, kernel@pengutronix.de, linux-can@vger.kernel.org
Subject: Re: pull-request: can-next 2018-11-28,pull-request: can-next 2018-11-28
Date: Wed, 28 Nov 2018 11:21:57 -0800 (PST) [thread overview]
Message-ID: <20181128.112157.1875553528431620394.davem@davemloft.net> (raw)
In-Reply-To: <98eab65a-24c5-aba6-d4f0-746d7758d5ce@pengutronix.de>
From: Marc Kleine-Budde <mkl@pengutronix.de>
Date: Wed, 28 Nov 2018 17:01:13 +0100
> ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git tags/linux-can-next-for-4.21-20181128
This doesn't work for me at all.
I'm not adding a custom .ssh config entry to point gitolite.kernel.org
to the same SSH key that I use for gitolite@ra.kernel.org, no way.
I don't want to see these SSH based URLs any more, they are a pain and
add overhead to my workflow.
Please just use plain git:// URLs, thank you.
next prev parent reply other threads:[~2018-11-29 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 16:01 pull-request: can-next 2018-11-28 Marc Kleine-Budde
2018-11-28 19:21 ` David Miller [this message]
2018-11-29 7:14 ` pull-request: can-next 2018-11-28,pull-request: " Marc Kleine-Budde
2018-11-29 7:19 ` pull-request: can-next 2018-11-28,pull-request: can-next 2018-11-28,Re: " David Miller
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=20181128.112157.1875553528431620394.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).