From: Junio C Hamano <junkio@cox.net>
To: Sven Verdoolaege <skimo@kotnet.org>
Cc: git@vger.kernel.org, "Randal L. Schwartz" <merlyn@stonehenge.com>
Subject: Re: openbsd version?
Date: Thu, 13 Oct 2005 00:47:26 -0700 [thread overview]
Message-ID: <7vpsq9504x.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vzmph1225.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Mon, 10 Oct 2005 14:42:42 -0700")
Junio C Hamano <junkio@cox.net> writes:
> Sven Verdoolaege <skimo@kotnet.org> writes:
>
>> I think you mean
>>
>> $ git-update-ref refs/heads/mybranch mybranch^
>
> Of course you are right. Thanks.
And I am an idiot. I did that myself again, and ended up
wasting 30 minutes or so, scratching my head.
Maybe there should be a safety measure built into git-update-ref
that says single-level name (i.e. not starting with refs/) gets
warning unless all uppercase or something silly like that to
protect idiots like myself. Hmmm.
next prev parent reply other threads:[~2005-10-13 7:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-10 16:12 openbsd version? Randal L. Schwartz
2005-10-10 16:29 ` Peter Eriksen
2005-10-10 16:41 ` Linus Torvalds
2005-10-10 19:06 ` Junio C Hamano
2005-10-10 19:29 ` Randal L. Schwartz
2005-10-10 20:30 ` Junio C Hamano
2005-10-10 20:36 ` Randal L. Schwartz
2005-10-10 20:49 ` Johannes Schindelin
2005-10-10 20:52 ` Randal L. Schwartz
2005-10-10 21:04 ` H. Peter Anvin
2005-10-10 21:05 ` Randal L. Schwartz
2005-10-10 21:31 ` Daniel Barkalow
2005-10-10 21:31 ` Junio C Hamano
2005-10-10 21:00 ` Sven Verdoolaege
2005-10-10 21:42 ` Junio C Hamano
2005-10-13 7:47 ` Junio C Hamano [this message]
2005-10-13 8:29 ` Sven Verdoolaege
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=7vpsq9504x.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=skimo@kotnet.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 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).