From: "Eric S. Raymond" <esr@thyrsus.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: 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: Sun, 6 Jan 2013 00:13:09 -0500 [thread overview]
Message-ID: <20130106051309.GB2303@thyrsus.com> (raw)
In-Reply-To: <20130105231151.GD3247@elie.Belkin>
Jonathan Nieder <jrnieder@gmail.com>:
> But in fact the current options list doesn't seem to be well organized at all.
I agree.
> 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
That would work as well or better than any other organization I can
think of. Um, which is significant because my work on surgery tools
and exporters means I've had to consult this page a *lot*.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2013-01-06 5:14 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 [this message]
2013-01-06 7:12 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130106051309.GB2303@thyrsus.com \
--to=esr@thyrsus.com \
--cc=b@rr-dav.id.au \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.