From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Mark Brown <broonie@sirena.org.uk>
Cc: Shuah Khan <shuah.kh@samsung.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [Ksummit-discuss] kselftest - What's in 3.17 and plans for 3.18 and beyond
Date: Wed, 13 Aug 2014 15:08:33 +0200 [thread overview]
Message-ID: <CAMuHMdVLMzFo-sB1HLO3vQkB4rdzvOgLnD=8-OR5SkKb13zRTw@mail.gmail.com> (raw)
In-Reply-To: <20140813124250.GT17528@sirena.org.uk>
Hi Mark,
On Wed, Aug 13, 2014 at 2:42 PM, Mark Brown <broonie@sirena.org.uk> wrote:
> On Wed, Aug 13, 2014 at 01:12:28PM +0200, Geert Uytterhoeven wrote:
>> On Wed, Aug 13, 2014 at 12:40 PM, Mark Brown <broonie@kernel.org> wrote:
>
>> > Kevin's copy is here:
>
>> > git://git.linaro.org/people/khilman/build-scripts.git
>
>> 404
>
>> Kevin's name got expanded:
>
>> git://git.linaro.org/people/kevin.hilman/build-scripts.git
>
> Interesting... how are you cloning? Both work for me:
>
> $ git clone git://git.linaro.org/people/khilman/build-scripts.git
> Cloning into 'build-scripts'...
> remote: Counting objects: 489, done.
> remote: Compressing objects: 100% (307/307), done.
> remote: Total 489 (delta 302), reused 295 (delta 181)
> Receiving objects: 100% (489/489), 73.90 KiB, done.
> Resolving deltas: 100% (302/302), done.
Bummer, I didn't clone, but opened
http://git.linaro.org/people/khilman/build-scripts.git in my web browser
by clicking on the link.
So Linaro gitweb supports the full names only, while real git can
access both (cloning indeed works for both).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2014-08-13 13:08 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 14:36 Shuah Khan
2014-08-07 18:24 ` Bird, Tim
2014-08-07 19:59 ` Shuah Khan
2014-08-08 2:18 ` Masami Hiramatsu
2014-08-11 14:11 ` Shuah Khan
2014-08-11 16:13 ` Masami Hiramatsu
2014-08-12 13:00 ` Grant Likely
2014-08-12 16:15 ` Guenter Roeck
2014-08-12 16:21 ` Masami Hiramatsu
2014-08-12 16:51 ` Geert Uytterhoeven
2014-08-12 17:15 ` Theodore Ts'o
2014-08-12 16:23 ` Grant Likely
2014-08-12 16:49 ` Mark Brown
2014-08-13 6:26 ` Grant Likely
2014-08-13 10:40 ` Mark Brown
2014-08-13 11:12 ` Geert Uytterhoeven
2014-08-13 12:42 ` Mark Brown
2014-08-13 13:08 ` Geert Uytterhoeven [this message]
2014-08-13 15:00 ` Kevin Hilman
2014-08-13 16:40 ` Olof Johansson
2014-08-13 17:11 ` Mark Brown
2014-08-12 17:46 ` Tim Bird
2014-08-12 18:06 ` Steven Rostedt
2014-08-12 20:52 ` Tim Bird
2014-08-14 16:35 ` Grant Likely
2014-08-12 17:30 ` Andy Lutomirski
2014-08-12 16:34 ` Shuah Khan
2014-08-13 8:35 ` Linus Walleij
2014-08-13 16:11 ` Guenter Roeck
2014-08-13 16:16 ` Andy Lutomirski
2014-08-13 16:44 ` Bird, Tim
2014-08-13 17:07 ` Grant Likely
2014-08-13 17:10 ` Andy Lutomirski
2014-08-13 17:10 ` Guenter Roeck
2014-08-18 3:10 ` Rob Landley
2014-08-18 3:08 ` Rob Landley
2014-08-18 7:16 ` Geert Uytterhoeven
2014-08-13 16:45 ` Masami Hiramatsu
2014-08-18 3:18 ` Rob Landley
2014-08-13 15:06 ` Aneesh Kumar K.V
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='CAMuHMdVLMzFo-sB1HLO3vQkB4rdzvOgLnD=8-OR5SkKb13zRTw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=broonie@sirena.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=shuah.kh@samsung.com \
/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