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

Re: [PATCH] reset: update help text

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 31, 2011, 18:45 UTC
Message-ID
<7v4o6jku28.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20110329210457.GA14031@elie>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 18 quoted lines
> The description does not make it obvious to me how these two (--merge
> and --keep) differ.  I think the intent of the options are:
>
>  --keep:
> 	start working on a different commit, carrying over local changes
> 	(like "git checkout")
>  --merge:
> 	return to <commit>, cancelling a merge-like operation that
> 	creates some unmerged and some clean index entries
>
> Maybe something along these lines could be ok starting point?
>
> 	OPT_SET_INT(0, "keep", &reset_type,
> 		"move to <commit>, carrying over local changes in working tree",
> 		KEEP),
> 	OPT_SET_INT(0, "merge", &reset_type,
> 		"return to <commit>, cancelling failed merge or cherry-pick",
> 		MERGE),

I cannot think of anything better, but I can still show my concern that "move to" and "return to" might not convey exactly what we are trying to express.

But I agree that your phrasing definitely is a good starting point.
Previous: Nguyen Thai Ngoc Duy
Message 9 of 9 in “reset: update help text”
  1. reset: update help textNguyễn Thái Ngọc Duy, Mar 29, 2011
  2. Nguyen Thai Ngoc DuyMar 29, 2011
  3. Jonathan NiederMar 29, 2011
  4. Nguyen Thai Ngoc DuyMar 31, 2011
  5. Jonathan NiederMar 31, 2011
  6. Junio C HamanoMar 31, 2011
  7. Jonathan NiederMar 31, 2011
  8. Nguyen Thai Ngoc DuyApr 2, 2011
  9. Junio C HamanoMar 31, 2011

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.