From: "Dmitry Potapov" <dpotapov@gmail.com>
To: Martin <html-kurs@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: remote does not support deleting refs
Date: Sun, 6 Jul 2008 17:29:33 +0400 [thread overview]
Message-ID: <37fcd2780807060629gbbbb2eai5ecfde6afe8c18b0@mail.gmail.com> (raw)
In-Reply-To: <486FE602.3060301@gmx.de>
On Sun, Jul 6, 2008 at 1:22 AM, Martin <html-kurs@gmx.de> wrote:
>
> To ssh://myserver.com/my/path/to/repository
> ! [rejected] testbranch (remote does not support deleting refs)
What version of Git do you use on the server? I think Git before v1.5 does
not support deleting remote refs. You have to upgrade Git on your server.
Dmitry
prev parent reply other threads:[~2008-07-06 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 21:22 remote does not support deleting refs Martin
2008-07-06 0:20 ` error: unlink(.git/refs/remotes/origin/testbranch) failed: was " Martin
2008-07-06 18:34 ` Dmitry Potapov
2008-07-08 4:08 ` Jeff King
2008-07-08 20:04 ` Junio C Hamano
2008-07-06 13:29 ` Dmitry Potapov [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=37fcd2780807060629gbbbb2eai5ecfde6afe8c18b0@mail.gmail.com \
--to=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=html-kurs@gmx.de \
/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).