From: Thomas Pasch <thomas.pasch@jentro.com>
To: Eygene Ryabinkin <rea-git@codelabs.ru>
Cc: git@vger.kernel.org
Subject: Re: git-http-push / webDAV
Date: Tue, 02 Oct 2007 13:15:35 +0200 [thread overview]
Message-ID: <47022857.806@jentro.com> (raw)
In-Reply-To: <20071002104646.GY975@void.codelabs.ru>
Dear Eygene,
I used a rather small test repo with only 2 or 3
commits.
The last tests I did with the a (current) git repo clone:
> git clone --bare git://git.kernel.org/pub/scm/git/git.git
e147e54b14828fa2e88e88907e0ca4dc3d694448 has indeed *not*
found its way into the http push repo. For me it looks
like that the push *first* updates refs/heads/master
(successfully) but fails to transfer the object itself.
Perhaps it would be more graceful that the object is
transfered *first* and then the remote tip is updated...
What version of git do you use?
Cheers,
Thomas
Eygene Ryabinkin wrote:
> Thomas,
>
> Tue, Oct 02, 2007 at 11:57:10AM +0200, Thomas Pasch wrote:
>> well, *somewhat* better with the trailing slash:
>>
>>> echo "modified" >>grep.c
>>> git commit -a
>> Created commit e147e54: mod
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>> git push -v
>> Pushing to http://test@x.x.x.x/git/git.git/
>> Fetching remote heads...
>> refs/
>> refs/heads/
>> refs/tags/
>> updating 'refs/heads/master'
>> from 34c6dbdef439f7cd93d3fe22493a3c1496ce96f7
>> to e147e54b14828fa2e88e88907e0ca4dc3d694448
>> sending 3 objects
>> done
>> Updating remote server info
>>
>> There's no more error message.
>
> OK, that's fine: the previous error was tied to the fact that
> when you're getting /git/git.git from the Web-server, it notices
> that it is a directory and redirects you to the /git/git.git/.
> But (IIRC) curl does not follow such redirections.
>
>> However, push has still
>> not worked. If I try to check out the new HEAD:
>>
>>> git clone http://test@x.x.x.x/git/git.git/
>> Initialized empty Git repository in /home/tpasch/tmp/git/.git/
>> Getting alternates list for http://test@x.x.x.x/git/git.git
>> Getting pack list for http://test@x.x.x.x/git/git.git
>> Getting index for pack 563e2090185692c7d765775569a0ce986840fd17
>> Getting pack 563e2090185692c7d765775569a0ce986840fd17
>> which contains 3af9d3e08da868c3a7687ab38d72f4296a99005d
>> [...]
>> walk 24778e335a6450e34257a311d0bf4a12bdb3006c
>> walk 19b2860cba5742ab31fd682b80fefefac19be141
>> walk bf0c6e839c692142784caf07b523cd69442e57a5
>> walk e497ea2a9b6c378f01d092c210af20cbee762475
>> walk 8bc9a0c769ac1df7820f2dbf8f7b7d64835e3c68
>> walk e83c5163316f89bfbde7d9ab23ca2e25604af290
>> Getting alternates list for http://test@x.x.x.x/git/git.git
>> Getting pack list for http://test@x.x.x.x/git/git.git
>> error: Unable to find e147e54b14828fa2e88e88907e0ca4dc3d694448 under
>> http://test@x.x.x.x/git/git.git
>> Cannot obtain needed object e147e54b14828fa2e88e88907e0ca4dc3d694448
>
> OK, I will try to do this on my server with 2.2.6. How big
> is your repository? Both size and commit number.
>
> Thanks.
next prev parent reply other threads:[~2007-10-02 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 13:31 git-http-push / webDAV Thomas Pasch
2007-10-01 15:54 ` Eygene Ryabinkin
2007-10-02 8:49 ` Thomas Pasch
2007-10-02 8:54 ` Eygene Ryabinkin
2007-10-02 9:57 ` Thomas Pasch
2007-10-02 10:46 ` Eygene Ryabinkin
2007-10-02 11:15 ` Thomas Pasch [this message]
2007-10-09 9:37 ` Thomas Pasch
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=47022857.806@jentro.com \
--to=thomas.pasch@jentro.com \
--cc=git@vger.kernel.org \
--cc=rea-git@codelabs.ru \
/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).