From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: openbsd version?
Date: 10 Oct 2005 13:36:01 -0700 [thread overview]
Message-ID: <86ek6tcdou.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <7vll113yjs.fsf@assigned-by-dhcp.cox.net>
>>>>> "Junio" == Junio C Hamano <junkio@cox.net> writes:
Junio> Removing non-current branch -- you may need to do -D instead of -d.
Junio> $ git branch -d mybranch
<sarcasm>Undocumented secret switches. Nice.</sarcasm> No wonder
I couldn't find it.
>> That's also a question in general... how can I remove a commit,
>> knowing that I'd never refer to it again? Or is disk space so cheap
>> that it wouldn't make any difference anyway?
Junio> Removing from the tip of the current branch:
Junio> $ git reset HEAD^
Junio> Removing from the tip of non-current branch:
Junio> $ git update-ref mybranch mybranch^
Do these also flush any related object files? Or do I need git-fsck still?
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2005-10-10 20:36 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 [this message]
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
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=86ek6tcdou.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).