git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: git@vger.kernel.org
Subject: Re: openbsd version?
Date: Mon, 10 Oct 2005 13:30:15 -0700	[thread overview]
Message-ID: <7vll113yjs.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <864q7pdvcn.fsf@blue.stonehenge.com> (Randal L. Schwartz's message of "10 Oct 2005 12:29:12 -0700")

merlyn@stonehenge.com (Randal L. Schwartz) writes:

> Related question.  I created "mybranch" to do the patch, but how
> can I have my repository now forget that mybranch was ever made?
> Is it sufficient to remove the branch link, and then type some "fsck"
> operation?

Removing non-current branch -- you may need to do -D instead of -d. 

$ git branch -d mybranch

> 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?

Removing from the tip of the current branch:

$ git reset HEAD^

Removing from the tip of non-current branch:

$ git update-ref mybranch mybranch^

  reply	other threads:[~2005-10-10 20:30 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 [this message]
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
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=7vll113yjs.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=merlyn@stonehenge.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).