From: Sverre Rabbelier <srabbelier@gmail.com>
To: John Williams <john.williams@petalogix.com>
Cc: Git Mailinglist <git@vger.kernel.org>
Subject: Re: Wierd git over http behaviour
Date: Fri, 20 Feb 2009 07:39:36 +0100 [thread overview]
Message-ID: <bd6139dc0902192239i3c5f196qf890c8b0a6f9ff46@mail.gmail.com> (raw)
In-Reply-To: <1d3f23370902192224g71270880p84e150af9640dec6@mail.gmail.com>
Heya,
On Fri, Feb 20, 2009 at 07:24, John Williams
<john.williams@petalogix.com> wrote:
> On Fri, Feb 20, 2009 at 4:19 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
>> This url seems to be broken/dead?
>
> bah - append .git :(
>
> http://developer.petalogix.com/git2/linux-2.6-microblaze.git
Ok, that works :).
--
Cheers,
Sverre Rabbelier
prev parent reply other threads:[~2009-02-20 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 6:13 Wierd git over http behaviour John Williams
2009-02-20 6:23 ` Junio C Hamano
2009-02-24 5:45 ` John Williams
[not found] ` <bd6139dc0902192219m21c6b4e6ne9bcd2ca4ef6a9b5@mail.gmail.com>
[not found] ` <1d3f23370902192224g71270880p84e150af9640dec6@mail.gmail.com>
2009-02-20 6:39 ` Sverre Rabbelier [this message]
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=bd6139dc0902192239i3c5f196qf890c8b0a6f9ff46@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=john.williams@petalogix.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;
as well as URLs for NNTP newsgroup(s).