From: Jonathan Nieder <jrnieder@gmail.com>
To: Bo Yang <struggleyb.nku@gmail.com>
Cc: git@vger.kernel.org, Thomas Rast <trast@student.ethz.ch>,
Jens Lehmann <Jens.Lehmann@web.de>,
Jakub Narebski <jnareb@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: Multiple line ranges and files in line level history browser
Date: Mon, 10 May 2010 04:31:20 -0500 [thread overview]
Message-ID: <20100510093120.GA4445@progeny.tock> (raw)
In-Reply-To: <20100509210654.GA1637@progeny.tock>
Jonathan Nieder wrote:
> If -- is found, any
> -L arguments before the -- apply to all files specified. Unclaimed
> arguments before the -- are revision specifiers.
More comments.
The -L arguments describe lines in some particular revision of the
files, so how would arbitrary ‘rev-list’-style revision specifiers
work here? They don’t: in ‘blame’, one "positive" revision is allowed
and the rest must be negative. Good.
The modified proposal was, roughly:
git blame [options, no -L among them] revs ((-L range)... filespec)...
git blame [options, -L permitted] revs -- [filespec...]
git blame [options, -L permitted] revs [filespec...]
“...” means “one or more”. How to know whether the -L or revision
arguments are encountered first? One approach is to abuse
STOP_AT_NON_OPTION to catch the -L, revisions, and filespecs as they
appear. Probably better would be to make -L an unknown option and
rely on parse_revision_opt leaving a residue of any revisions it
finds, so that after the first pass, the first syntax can be
distinguished from the others by the first argument starting with "-L".
Feel free to do something else entirely (including another syntax) if
you prefer, of course.
Here’s a patch that makes STOP_AT_NON_OPTION easier to abuse, without
affecting current users. Maybe it would make it easier to play
around.
Good night,
Jonathan
parse-options.c | 3 ++-
parse-options.h | 1 +
2 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/parse-options.c b/parse-options.c
index 8546d85..4e3532b 100644
--- a/parse-options.c
+++ b/parse-options.c
@@ -372,7 +372,7 @@ int parse_options_step(struct parse_opt_ctx_t *ctx,
if (parse_nodash_opt(ctx, arg, options) == 0)
continue;
if (ctx->flags & PARSE_OPT_STOP_AT_NON_OPTION)
- break;
+ return PARSE_OPT_NON_OPTION;
ctx->out[ctx->cpidx++] = ctx->argv[0];
continue;
}
@@ -454,6 +454,7 @@ int parse_options(int argc, const char **argv, const char *prefix,
switch (parse_options_step(&ctx, options, usagestr)) {
case PARSE_OPT_HELP:
exit(129);
+ case PARSE_OPT_NON_OPTION:
case PARSE_OPT_DONE:
break;
default: /* PARSE_OPT_UNKNOWN */
diff --git a/parse-options.h b/parse-options.h
index 7581e93..4773cf9 100644
--- a/parse-options.h
+++ b/parse-options.h
@@ -160,6 +160,7 @@ extern NORETURN void usage_msg_opt(const char *msg,
enum {
PARSE_OPT_HELP = -1,
PARSE_OPT_DONE,
+ PARSE_OPT_NON_OPTION,
PARSE_OPT_UNKNOWN,
};
--
1.7.1
next prev parent reply other threads:[~2010-05-10 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-09 14:00 Multiple line ranges and files in line level history browser Bo Yang
2010-05-09 18:20 ` Junio C Hamano
2010-05-11 5:43 ` Bo Yang
2010-05-12 7:57 ` Thomas Rast
2010-05-09 21:06 ` Jonathan Nieder
2010-05-10 9:31 ` Jonathan Nieder [this message]
2010-05-11 6:28 ` Bo Yang
2010-05-11 6:16 ` Bo Yang
2010-05-11 6:28 ` 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=20100510093120.GA4445@progeny.tock \
--to=jrnieder@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=johannes.schindelin@gmx.de \
--cc=struggleyb.nku@gmail.com \
--cc=trast@student.ethz.ch \
/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).