From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Michael Hendricks <michael@ndrix.org>, git@vger.kernel.org
Subject: Re: removing content from git history
Date: Wed, 21 Feb 2007 12:17:38 -0500 [thread overview]
Message-ID: <20070221171738.GA9112@fieldses.org> (raw)
In-Reply-To: <20070221165636.GH25559@spearce.org>
On Wed, Feb 21, 2007 at 11:56:36AM -0500, Shawn O. Pearce wrote:
> Now this is actually not a huge deal if you do it on your local
> repository and go "whoops, I should not have committed that". If you
> have not yet pushed the commit to another repository (and someone
> has not yet fetched it from you either) you can use git-rebase to
> discard it.
Also it can't have done any (non-fast-forward) merges since then.
Reconstructing history with a bunch of merges seems like something that
could be a huge pain. (Though with some tools it might be doable.)
--b.
next prev parent reply other threads:[~2007-02-21 17:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-21 16:45 removing content from git history Michael Hendricks
2007-02-21 16:56 ` Shawn O. Pearce
2007-02-21 17:17 ` J. Bruce Fields [this message]
2007-02-21 18:02 ` Linus Torvalds
2007-02-21 18:24 ` Linus Torvalds
2007-02-21 21:00 ` Shawn O. Pearce
2007-02-21 21:11 ` Linus Torvalds
2007-02-21 21:21 ` Shawn O. Pearce
2007-10-09 20:58 ` Bill Lear
2007-10-09 21:02 ` J. Bruce Fields
2007-10-09 22:25 ` Bill Lear
2007-10-10 14:41 ` Johannes Schindelin
2007-02-21 17:14 ` Linus Torvalds
2007-02-21 18:02 ` Nicolas Pitre
2007-02-21 18:13 ` Linus Torvalds
2007-02-21 18:39 ` Nicolas Pitre
2007-02-21 18:30 ` Michael Hendricks
2007-02-21 18:37 ` Shawn O. Pearce
2007-02-21 18:47 ` Linus Torvalds
2007-02-21 18:56 ` Linus Torvalds
2007-02-21 18:52 ` Nicolas Pitre
2007-02-21 19:01 ` Junio C Hamano
2007-02-21 19:33 ` Nicolas Pitre
2007-02-21 20:22 ` Junio C Hamano
2007-02-21 20:49 ` Nicolas Pitre
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=20070221171738.GA9112@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=michael@ndrix.org \
--cc=spearce@spearce.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.