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

Re: [PATCH] Alphabetize the fast-import options, following a suggestion on the list.

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jan 5, 2013, 23:11 UTC
Message-ID
<20130105231151.GD3247@elie.Belkin>
In-Reply-To
<20130105164415.39B144044B@snark.thyrsus.com>
Eric S. Raymond wrote:
> ---

Missing sign-off. Depending on when you prefer to add the sign-off, something like

	echo '[alias] c = commit --signoff' >>~/.gitconfig
or
	echo '[alias] f = format-patch --signoff' >>~/.gitconfig

might be useful for the future, assuming you already look over what you are sending out in a mail client to avoid mistakes.

> Documentation/git-fast-import.txt | 94 +++++++++++++++++++--------------------
> 1 file changed, 45 insertions(+), 49 deletions(-)

My knee-jerk response was "If the options are currently organized logically, wouldn't it be more appropriate to add a sub-heading for each group of options and alphabetize only within the subgroups?"

But in fact the current options list doesn't seem to be well organized at all. What do you think would be a logical way to group these?

 Features of input syntax
	--date-format
	--done
 Verbosity
	--quiet
	--stats
 Marks handling (checkpoint/restore)
	--import-marks
	--import-marks-if-exists
	--export-marks
	--relative-marks
 Semantics of execution
	--dry-run
	--force
	--cat-blob-fd
	--export-pack-edges
 Tuning
	--active-branches
	--max-pack-size
	--big-file-threshold
	--depth
Previous: Eric S. RaymondNext: Eric S. Raymond
Message 2 of 9 in “Alphabetize the fast-import options, following a suggestion on the list.”
  1. Alphabetize the fast-import options, following a suggestion on the list.Eric S. Raymond, Jan 5, 2013
  2. Jonathan NiederJan 5, 2013
  3. Eric S. RaymondJan 6, 2013
  4. Junio C HamanoJan 6, 2013
  5. git-fast-import(1): reorganise optionsJohn Keeping, Jan 6, 2013
  6. Jonathan NiederJan 6, 2013
  7. John KeepingJan 6, 2013
  8. Junio C HamanoJan 6, 2013
  9. fast-import doc: split OPTIONS into subsectionsJonathan Nieder, Jan 6, 2013

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.