From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Eric S. Raymond" <esr@thyrsus.com>,
git@vger.kernel.org, David Michael Barr <b@rr-dav.id.au>,
Pete Wyckoff <pw@padd.com>
Subject: Re: [PATCH] Alphabetize the fast-import options, following a suggestion on the list.
Date: Sat, 05 Jan 2013 23:12:25 -0800 [thread overview]
Message-ID: <7vy5g6okdi.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130105231151.GD3247@elie.Belkin> (Jonathan Nieder's message of "Sat, 5 Jan 2013 15:11:51 -0800")
Jonathan Nieder <jrnieder@gmail.com> writes:
> 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
Sounds sensible.
next prev parent reply other threads:[~2013-01-06 7:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-05 16:44 [PATCH] Alphabetize the fast-import options, following a suggestion on the list Eric S. Raymond
2013-01-05 23:11 ` Jonathan Nieder
2013-01-06 5:13 ` Eric S. Raymond
2013-01-06 7:12 ` Junio C Hamano [this message]
2013-01-06 13:29 ` [PATCH] git-fast-import(1): reorganise options John Keeping
2013-01-06 13:51 ` Jonathan Nieder
2013-01-06 14:28 ` John Keeping
2013-01-06 23:10 ` Junio C Hamano
2013-01-09 19:43 ` [PATCH v2 0/2] Reorganise options in git-fast-import(1) John Keeping
2013-01-09 19:44 ` [PATCH v2 1/2] git-fast-import(1): combine documentation of --[no-]relative-marks John Keeping
2013-01-09 21:42 ` Jonathan Nieder
2013-01-09 19:45 ` [PATCH v2 2/2] git-fast-import(1): reorganise options John Keeping
2013-01-09 22:21 ` Junio C Hamano
2013-01-06 13:34 ` [PATCH/RFC] fast-import doc: split OPTIONS into subsections Jonathan Nieder
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=7vy5g6okdi.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=b@rr-dav.id.au \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=pw@padd.com \
/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).