From: Thomas Jarosch <thomas.jarosch@intra2net.com>
To: git@vger.kernel.org
Cc: Steve <shrotty@gmx.ch>
Subject: Re: git-push on packed refs via HTTP
Date: Fri, 20 Mar 2009 11:03:59 +0100 [thread overview]
Message-ID: <200903201103.59907.thomas.jarosch@intra2net.com> (raw)
In-Reply-To: <loom.20090320T094550-421@post.gmane.org>
Hi Steve,
On Friday, 20. March 2009 10:50:57 you wrote:
> Using HTTP as transport, I've noticed that after using git-gc on a git
> server, I can't push to that repo anymore: "No refs in common and none
> specified." Client and server are both 1.6.2. Is ths a bug or do I have to
> do something after executing git-gc on the server?
Check the permissions of the files on the server, I once accidentally executed
git commands as root user and the HTTP server was later
unable to read/write the repository properly.
Thomas
next prev parent reply other threads:[~2009-03-20 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 9:50 git-push on packed refs via HTTP Steve
2009-03-20 10:03 ` Thomas Jarosch [this message]
2009-03-20 10:25 ` Steve
2009-03-20 10:38 ` Andreas Ericsson
2009-03-20 10:50 ` Steve
2009-03-20 12:00 ` Tay Ray Chuan
2009-03-20 12:31 ` Steve
2009-03-20 12:45 ` Johannes Schindelin
2009-03-27 10:20 ` Steve
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=200903201103.59907.thomas.jarosch@intra2net.com \
--to=thomas.jarosch@intra2net.com \
--cc=git@vger.kernel.org \
--cc=shrotty@gmx.ch \
/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).