From: Pierre Habouzit <madcoder@debian.org>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] convert shortlog to use parse_options
Date: Sun, 02 Mar 2008 09:11:40 +0100 [thread overview]
Message-ID: <20080302081139.GA5407@artemis.madism.org> (raw)
In-Reply-To: <20080302061541.GA3935@coredump.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]
On Sun, Mar 02, 2008 at 06:15:42AM +0000, Jeff King wrote:
> #define OPT__REVISION(x) \
> OPT_BOOLEAN(0, "no-merges", &(x)->no_merges, "don't show merges"),
> OPT_BOOLEAN(0, "boundary", &(x)->boundary, "show boundary commits"),
> ...
>
> and we could have unified options tables. I seem to recall some work
> being done in this area early on in the parse-options history, but I
> can't seem to find any mention of it in the list archive. Pierre, does
> this ring a bell?
Yes, I didn't had the time to finish that, I just started some ground
works in the diff options area, I hope I didn't lost that work, it's
probably somewhere on my public repository. Though revision parsing are
special because of --not, but I think the proper solution wrt --not and
--all in revision parsing is to ask parse-opt to "let" some options stay
as arguments, and do the final revision parsing with them kept.
Like you may have noticed, I didn't have a lot of time for git
recently, and that's a shame :| But maybe your mail will beat me into
working on this again now that 1.5.4 is released, because I also feared
that reworking diff and revision parsing options will probably introduce
quite a few regressions, and it's rather better doing so at the
beginning of a release cycle :)
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-02 8:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 9:02 [PATCH] convert shortlog to use parse_options Jeff King
2008-03-01 9:37 ` Junio C Hamano
2008-03-02 6:15 ` Jeff King
2008-03-02 8:11 ` Pierre Habouzit [this message]
2008-03-02 8:29 ` Pierre Habouzit
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=20080302081139.GA5407@artemis.madism.org \
--to=madcoder@debian.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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 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 NNTP newsgroup(s).