From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Jeff Garzik <jeff@garzik.org>
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 11:07:09 +0400 [thread overview]
Message-ID: <20080526070708.GB16366@2ka.mipt.ru> (raw)
In-Reply-To: <483A59D7.7020306@garzik.org>
On Mon, May 26, 2008 at 02:33:59AM -0400, Jeff Garzik (jeff@garzik.org) wrote:
> >No it should be cc4d281eb8d9a4d3a5610acf1558c327358f5725
> >Author: Evgeniy Polyakov johnpol@2ka.mipt.ru <zbr@gavana.yandex.ru>
> >Date: Sun May 25 17:24:56 2008 +0400
> >
> > Kconfig entries for cc group and debugging.
> >
> >I used 'git push remote_repo' to push data after repository was create,
> >probably I
> >should use 'git push --all remote_repo', please try again.
>
> Nope.
>
> Did you forget git-update-server-info, since your method is HTTP?
At least on server HEAD (refs/heads/master) points to
cc4d281eb8d9a4d3a5610acf1558c327358f5725
I tries git-update-server-info on client and pushed all again, but it
returned that everything is up-to-date.
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-05-26 7:07 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 [this message]
2008-05-26 7:27 ` Jeff Garzik
2008-05-26 7:44 ` Evgeniy Polyakov
2008-05-26 7:51 ` Jeff Garzik
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=20080526070708.GB16366@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=jeff@garzik.org \
--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 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).