From: Tomas Carnecky <tom@dbservice.com>
To: Jingzhao Ou <jingzhao.ou@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Unable to delete remote branch with a strange name
Date: Tue, 28 Dec 2010 18:59:29 +0100 [thread overview]
Message-ID: <4D1A2581.9050305@dbservice.com> (raw)
In-Reply-To: <loom.20101228T170808-756@post.gmane.org>
On 12/28/10 5:10 PM, Jingzhao Ou wrote:
> Yes, using the absolute path works like a champ!
>
> git push origin :refs/heads/remotes/origin/dev/main
Do not use the term 'path' in this context. The fact that a ref looks
like a path, and can be stored on the filesystem under the same
directory structure is just an implementation detail. Note the *can*,
because in the case of packed refs (see man git-pack-refs) the term
'path' is not even remotely accurate.
We use the term 'fully qualified ref' (see the similarity with 'fully
qualified domain name') if we want to stress out that the full name of
the ref is used (refs/heads/foo) instead of an abbreviation (foo).
tom
prev parent reply other threads:[~2010-12-28 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 7:06 Unable to delete remote branch with a strange name Jingzhao Ou
2010-12-28 8:40 ` Andreas Schwab
2010-12-28 16:10 ` Jingzhao Ou
2010-12-28 17:59 ` Tomas Carnecky [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=4D1A2581.9050305@dbservice.com \
--to=tom@dbservice.com \
--cc=git@vger.kernel.org \
--cc=jingzhao.ou@gmail.com \
/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).