From: "Christof Krüger" <git@christof-krueger.de>
To: Shantanu Pavgi <pavgi@uab.edu>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: removing files from history but not filesystem
Date: Wed, 29 Jun 2011 18:57:10 +0200 [thread overview]
Message-ID: <1309366630.2417.51.camel@oxylap> (raw)
In-Reply-To: <1309327707.2417.49.camel@oxylap>
> Another possible way would be to create a temporary branch to point at
> HEAD^, filter-branch it, then add a graft to stitch the remaining commit
> on top of it, then filter-branch HEAD and then remove the branch. But
> this is a bit advanced for the case where you just want to omit one
> commit.
That should have been "[...] and then remove the _graft_." (and the
temporary branch).
Regards,
Chris
next prev parent reply other threads:[~2011-06-29 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 6:13 removing files from history but not filesystem Shantanu Pavgi
2011-06-28 7:04 ` Christof Krüger
2011-06-29 4:10 ` Shantanu Pavgi
2011-06-29 6:08 ` Christof Krüger
2011-06-29 16:57 ` Christof Krüger [this message]
2011-06-29 21:45 ` Shantanu Pavgi
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=1309366630.2417.51.camel@oxylap \
--to=git@christof-krueger.de \
--cc=git@vger.kernel.org \
--cc=pavgi@uab.edu \
/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).