From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: how to get your linux-2.6-virtex tree?
Date: Sat, 25 Aug 2007 10:29:35 -0400 [thread overview]
Message-ID: <9e4733910708250729k1d47c513ub5e62267a4884fc4@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40708250710q72bdaa90na4974f1af6030997@mail.gmail.com>
On 8/25/07, Grant Likely <grant.likely@secretlab.ca> wrote:
> Hmmm.... Works fine from my machines.
>
> grant@trillian:~/temp$ git-clone
> git://git.secretlab.ca/git/linux-2.6-virtex.git
I just checked it for you, both http and git are working.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2007-08-25 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 3:11 Problems on porting linux 2.6 to xilinx ML410 woyuzhilei
2007-08-24 18:21 ` Grant Likely
2007-08-25 7:37 ` woyuzhilei
2007-08-25 8:48 ` how to get your linux-2.6-virtex tree? Ming Liu
2007-08-25 14:10 ` Grant Likely
2007-08-25 14:29 ` Jon Smirl [this message]
2007-08-25 14:46 ` Ming Liu
2007-08-25 15:24 ` Grant Likely
2007-08-25 16:13 ` Ming Liu
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=9e4733910708250729k1d47c513ub5e62267a4884fc4@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.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).