git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Christian Couder <chriscool@tuxfamily.org>
To: Hal Eisen <eisen@dunhackin.org>
Cc: git@vger.kernel.org
Subject: Re: Question about git revert
Date: Thu, 8 Jul 2010 05:05:02 +0200	[thread overview]
Message-ID: <201007080505.02633.chriscool@tuxfamily.org> (raw)
In-Reply-To: <20100708015019.GP10042@volcano.builtonlinux.com>

On Thursday 08 July 2010 03:50:19 Hal Eisen wrote:
> I did a search of the archives for this mailing list, and couldn't
> find anything applicable.
> 
> I am having the same problem as Joshua Cheek.  He asked this question
> on StackOverflow about a month ago.
> 
> http://stackoverflow.com/questions/2938301/git-remove-specific-commit
> 
> There are no merges involved.  I would be perfectly happy having
> another commit in my history which documents the reverting of a prior
> commit.
> 
> The problem seems to stem from git-revert not properly calculating the
> "cleanness" of the prior commit, and incorrectly thinking that later
> commits depend on the to-be-reverted commit.

You may want to try "git revert" with the new --strategy option,
for example "git revert --strategy resolve <commit>". This option is not in a 
released version yet, so you should use one of the last git version from the 
master branch, for example v1.7.2-rc2.

> I have seen other web sites which suggest using git to manually
> generate a diff, and then applying it as a reverse patch, but that
> seems like a kludge.
> 
> What is the best solution for this use case?

It depends on how well the revert algorithms work in the case you are 
interested in. If one strategy works quite well, then manually fixing the few 
remaining problems, if any, in the result is probably the best solution. 

Regards,
Christian.

  reply	other threads:[~2010-07-08  3:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08  1:50 Question about git revert Hal Eisen
2010-07-08  3:05 ` Christian Couder [this message]
2010-07-08  4:51 ` Elijah Newren

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201007080505.02633.chriscool@tuxfamily.org \
    --to=chriscool@tuxfamily.org \
    --cc=eisen@dunhackin.org \
    --cc=git@vger.kernel.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).