From: Julian Phillips <julian@quantumfyre.co.uk>
To: Evan Carroll <me@evancarroll.com>
Cc: git@vger.kernel.org
Subject: Re: Problem with http-repos vs filesys-remote-repos
Date: Fri, 10 Aug 2007 01:04:36 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708100101570.26697@beast.quantumfyre.co.uk> (raw)
In-Reply-To: <428b865e0708091640x715a5950x128da5da493cef2@mail.gmail.com>
On Thu, 9 Aug 2007, Evan Carroll wrote:
> A disclaimer:: I could have mucked with anything, I will not place the
> blame on git as if I had strictly adhered to the tutorial
> instructions. Anything I did was through the UI, there was no mucking
> with files. Thanks in advance and good luck:
>
> I have one repos located on /var/git/scraper.git, it houses a
> small-inhouse project which I'm trying to use to sell git with.
> Unfortunately, I've had a very difficult time doing everything with
> git. Namely, pulling and pushing. It appears as if I git-clone this
> using the file-system (fs) addressing I get a repos which `git log`
> shows was last modified on Aug 9th. However, if I check this out with
> a git-clone using apache, which is simply hosting
> /var/git/scraper.git, I get a repos which was last updated on aug 7th
> - thus it is missing *a lot* of devel time. Now the 7th was when I
> created the --bare repos from my working directory git. All of the
> gits involved are using the latest stable version 1.5.2.4, they all
> built cleanly. The log is as follows:
Have you enabled the post-update hook on your server (chmod +X
/var/git/scraper.git/hooks/post-update)? You need to run "git
update-server-info" after updating a repo to allow clones via http to work
properly. The default post-update hook does this for you.
--
Julian
---
No, I do not know what the Schadenfreude is. Please tell me, because
I'm dying to know.
-- Homer Simpson
When Flanders Failed
prev parent reply other threads:[~2007-08-10 0:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 23:40 Problem with http-repos vs filesys-remote-repos Evan Carroll
2007-08-10 0:04 ` Julian Phillips [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=Pine.LNX.4.64.0708100101570.26697@beast.quantumfyre.co.uk \
--to=julian@quantumfyre.co.uk \
--cc=git@vger.kernel.org \
--cc=me@evancarroll.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).