All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: linuxppc-dev@ozlabs.org
Subject: Git Clone/Fetch Advice
Date: Sat, 25 Aug 2007 09:50:45 -0500	[thread overview]
Message-ID: <E1IOwyL-0004fq-Tb@jdl.com> (raw)

Folks,

As someone who runs a git server _and_ reads their log files,
I would like to offer a few words of advice about cloning or
fetching git repositories.

First, watch those project path names carefully.  If someone
publishes a "linux-2.6-quux.git" repository, don't call it
the "linux-2.6.git" repository in your clone or fetch request.
And, oddly, don't call it "linux-2.6.quux.git" either! :-)

Second, upgrade your git installation.  I repeatedly see failed
clone requests due to outdated git clients trying to do a clone
or a fetch.  If you _know_ you have the clone path to the project
right, and it still doesn't seem to work, chance are very good
that you are using a git earlier than v1.4.2.  It is now time
to find something v1.5 or better.  1.5.3 is due out Real Soon Now!

I publish a _few_ repositories, and I see maybe 20 or 30 such
failed clone/fetch requests per day.  I hate to imagine what
the failure rate on kernel.org is!

Thanks,
jdl

                 reply	other threads:[~2007-08-25 14:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E1IOwyL-0004fq-Tb@jdl.com \
    --to=jdl@jdl.com \
    --cc=linuxppc-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.