From: Jeff Garzik <jeff@garzik.org>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: POHMELFS high performance network filesystem. Cache coherency, transactions, parallels.
Date: Mon, 26 May 2008 03:51:23 -0400 [thread overview]
Message-ID: <483A6BFB.1080209@garzik.org> (raw)
In-Reply-To: <20080526074424.GA555@2ka.mipt.ru>
Evgeniy Polyakov wrote:
> On Mon, May 26, 2008 at 03:27:59AM -0400, Jeff Garzik (jeff@garzik.org) wrote:
>> git-update-server-info needs to be run on the server, not the client.
>>
>> You can automate this by running this on the server:
>>
>> chmod +x .git/hooks/post-update
>>
>> so that git-update-server-info always runs on the server, after each push.
>>
>> See git-update-server-info(1) for more info.
>
> Hmm... Nothing can be run on server, since git does not believe it is in
> git repo:
Sorry, I should have mentioned, you need to set GIT_DIR environment
variable, for this case. e.g.
cd /home/s0mbre/archive/pohmelfs
GIT_DIR=pohmelfs.git git-update-server-info
or
cd /home/s0mbre/archive/pohmelfs/pohmelfs.git
GIT_DIR=. git-update-server-info
Regards,
Jeff
next prev parent reply other threads:[~2008-05-26 7:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-25 13:40 POHMELFS high performance network filesystem. Cache coherency, transactions, parallels Evgeniy Polyakov
2008-05-25 19:55 ` Jeff Garzik
2008-05-25 20:21 ` Evgeniy Polyakov
2008-05-26 1:15 ` Jeff Garzik
2008-05-26 6:22 ` Evgeniy Polyakov
2008-05-26 6:33 ` Jeff Garzik
2008-05-26 7:07 ` Evgeniy Polyakov
2008-05-26 7:27 ` Jeff Garzik
2008-05-26 7:44 ` Evgeniy Polyakov
2008-05-26 7:51 ` Jeff Garzik [this message]
2008-05-26 9:13 ` Evgeniy Polyakov
2008-05-26 1:41 ` Jeff Garzik
2008-05-26 7:12 ` Evgeniy Polyakov
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=483A6BFB.1080209@garzik.org \
--to=jeff@garzik.org \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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.