All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin <html-kurs@gmx.de>
To: git@vger.kernel.org
Subject: error: unlink(.git/refs/remotes/origin/testbranch) failed: was  remote does not support deleting refs
Date: Sun, 06 Jul 2008 02:20:18 +0200	[thread overview]
Message-ID: <48700FC2.8080307@gmx.de> (raw)
In-Reply-To: <486FE602.3060301@gmx.de>

Hi,

it seems that an old verison on the remote site was the problem:
On debian/etch git seems to be too old. I upgraded git to the testing 
version and now I can delete remote branches.

But I get another error:
$ git push origin :testbranch
To ssh://myserver.com/my/path/to/repository
  - [deleted]         testbranch
error: unlink(.git/refs/remotes/origin/testbranch) failed: No such file 
or directory
error: Failed to delete

Any idea?

Thanks,
Martin

Martin schrieb:
> Hi,
> 
> I tried to setup a central git repository. Access is via ssh.
> How do I delete a remote branch? If I try it using
>  > git branch -d -r origin/testbranch
>  > git push origin :refs/heads/testbranch
> I get the error
> 
> To ssh://myserver.com/my/path/to/repository
>  ! [rejected]        testbranch (remote does not support deleting refs)
> error: failed to push some refs to 
> 'ssh://myserver.com/my/path/to/repository'
> 
> So how do I setup my remote repository to allow deleting remote branches?
> 
> Thanks,
> Martin
> -- 
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2008-07-06  0:21 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 ` Martin [this message]
2008-07-06 18:34   ` error: unlink(.git/refs/remotes/origin/testbranch) failed: was " Dmitry Potapov
2008-07-08  4:08     ` Jeff King
2008-07-08 20:04       ` Junio C Hamano
2008-07-06 13:29 ` Dmitry Potapov

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=48700FC2.8080307@gmx.de \
    --to=html-kurs@gmx.de \
    --cc=git@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.