git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] prepare deprecation of git-revert

From
Pierre Habouzit <madcoder@debian.org>
Date
Oct 31, 2008, 15:57 UTC
Message-ID
<20081031155729.GB627@artemis.corp>
In-Reply-To
<1225468527-29694-1-git-send-email-madcoder@debian.org>
On Fri, Oct 31, 2008 at 03:55:27PM +0000, Pierre Habouzit wrote:
Show 39 quoted lines
> * Rename builtin-revert.c into builtin-cherry-pick.c
> 
> * Add option -R/--revert to git-cherry-pick.
>   Document it by taking the current content of git-revert manpage for the
>   option.
> 
> * get rid of the no_replay initialization, just ignore it when we're in
>   the revert case, it makes really no sense to error out.
> 
> * put the warning of deprecation in cmd_revert, #if 0-ed out for now.
> 
> Signed-off-by: Pierre Habouzit <madcoder@debian.org>
> ---
> 
>  I've not kept the auto-edit feature of git-revert for the git-cherry-pick -R
>  case as I don't believe it makes a lot of sense. But if people are unhappy
>  with that, I can easily "fix" it.
> 
>  Documentation/git-cherry-pick.txt         |   15 +++++++++++++++
>  Makefile                                  |    6 +++---
>  builtin-revert.c => builtin-cherry-pick.c |   10 ++++------
>  3 files changed, 22 insertions(+), 9 deletions(-)
>  rename builtin-revert.c => builtin-cherry-pick.c (98%)
> 
> diff --git a/Documentation/git-cherry-pick.txt b/Documentation/git-cherry-pick.txt
> index 837fb08..2d92f2d 100644
> --- a/Documentation/git-cherry-pick.txt
> +++ b/Documentation/git-cherry-pick.txt
> @@ -40,6 +40,21 @@ OPTIONS
>  	development branch), adding this information can be
>  	useful.
>  
> +-R::
> +--revert::
> +	Given one existing commit, revert the change the patch introduces, and
> +	record a new commit that records it.  This requires your working tree
> +	to be clean (no modifications from the HEAD commit).
> ++
> +Note: 'git revert' is used to record a new commit to reverse the
         ^ this was supposed to spell out 'git cherry-pick -R' of course :/
Show 7 quoted lines
> +effect of an earlier commit (often a faulty one).  If you want to
> +throw away all uncommitted changes in your working directory, you
> +should see linkgit:git-reset[1], particularly the '--hard' option.  If
> +you want to extract specific files as they were in another commit, you
> +should see linkgit:git-checkout[1], specifically the 'git checkout
> +<commit> -- <filename>' syntax.  Take care with these alternatives as
> +both will discard uncommitted changes in your working directory.
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org
Previous: Pierre HabouzitNext: Jakub Narebski
Message 2 of 16 in “prepare deprecation of git-revert”
  1. prepare deprecation of git-revertPierre Habouzit, Oct 31, 2008
  2. Pierre HabouzitOct 31, 2008
  3. Jakub NarebskiOct 31, 2008
  4. Pierre HabouzitOct 31, 2008
  5. Theodore TsoOct 31, 2008
  6. Andreas EricssonNov 1, 2008
  7. Alex RiesenOct 31, 2008
  8. Pierre HabouzitOct 31, 2008
  9. Alex RiesenOct 31, 2008
  10. Johannes SchindelinOct 31, 2008
  11. Junio C HamanoOct 31, 2008
  12. Matthieu MoyNov 1, 2008
  13. Nguyen Thai Ngoc DuyNov 2, 2008
  14. Johannes SchindelinNov 2, 2008
  15. Jeff KingNov 2, 2008
  16. Pierre HabouzitNov 2, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.