From: Ralf Baechle <ralf@linux-mips.org>
To: Pak Woon <pak.woon@nec.com.au>
Cc: linux-mips@linux-mips.org
Subject: Re: Introduction and problems cloning repository
Date: Fri, 29 Sep 2006 10:49:44 +0100 [thread overview]
Message-ID: <20060929094944.GA10597@linux-mips.org> (raw)
In-Reply-To: <451C7CE7.8040909@nec.com.au>
On Fri, Sep 29, 2006 at 11:54:47AM +1000, Pak Woon wrote:
> First time poster to this mailing list so if I am not following the
> correct protocol please let me know.
>
> Introduction. I am a firmware developer working for NEC Australia. We
> are currently developing a MIPS SOC device made by Wintegra.
>
> I am trying to clone the linux-malta.git repository using the command
> "git clone http://ftp.linux-mips.org/pub/scm/linux-malta.git
> ./linux-malta.git" but I receieve an "error: Can't lock ref". I have to
> use http because I am sure port 9418 is blocked by the sysadmin
An good old access permission problem on the web server but I won't have
time to sort it out now.
Until then you can use gitcvs to access the repositories:
cvs -d :pserver:anonymous@git.linux-mips.org:/pub/scm/linux.git co -d linux-malta -P <branch>
Where <branch> is one of linux-2.0, linux-2.2, linux-2.4, MaltaRef_2_4,
MaltaRef_2_6 and master - if your firewall allows port 2401 that is ...
But why are you still using the linux-malta repository? Since ~ 5 months
it is no longer being updated and has effectivly been replaced with
linux.git repository. Of this repository there are also snapshots of all
tagged versions available.
Ralf
next prev parent reply other threads:[~2006-09-29 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 1:54 Introduction and problems cloning repository Pak Woon
2006-09-29 9:49 ` Ralf Baechle [this message]
2006-09-29 17:52 ` Andrew Sharp
2006-10-02 1:37 ` Pak Woon
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=20060929094944.GA10597@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=pak.woon@nec.com.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox