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

Re: [PATCH 2/2] Add revision range support on "-" and "@{-1}"

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 16, 2015, 18:22 UTC
Message-ID
<xmqqlhiwredj.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1426518703-15785-3-git-send-email-kenny.lee28@gmail.com>
Kenny Lee Sin Cheong <kenny.lee28@gmail.com> writes:
Show 23 quoted lines
> diff --git a/revision.c b/revision.c
> index 7778bbd..a79b443 100644
> --- a/revision.c
> +++ b/revision.c
> @@ -1490,6 +1490,7 @@ int handle_revision_arg(const char *arg_, struct rev_info *revs, int flags, unsi
>  		int symmetric = *next == '.';
>  		unsigned int flags_exclude = flags ^ (UNINTERESTING | BOTTOM);
>  		static const char head_by_default[] = "HEAD";
> +		static const char prev_rev[] = "@{-1}";
>  		unsigned int a_flags;
>  
>  		*dotdot = 0;
> @@ -1499,6 +1500,13 @@ int handle_revision_arg(const char *arg_, struct rev_info *revs, int flags, unsi
>  			next = head_by_default;
>  		if (dotdot == arg)
>  			this = head_by_default;
> +		/*  Allows -..<rev> and <rev>..- */
> +		if (!strcmp(this, "-")) {
> +			this = prev_rev;
> +		}
> +		if (!strcmp(next, "-")) {
> +			next = prev_rev;
> +		}

The above two hunks are disappointing. "this" and "next" are passed to get_sha1_committish() and the point of the [1/2] patch was to allow "-" to be just as usable as "@{-1}" anywhere a branch name can be used.

Show 9 quoted lines
>  		if (this == head_by_default && next == head_by_default &&
>  		    !symmetric) {
>  			/*
> @@ -2198,7 +2206,7 @@ int setup_revisions(int argc, const char **argv, struct rev_info *revs, struct s
>  	read_from_stdin = 0;
>  	for (left = i = 1; i < argc; i++) {
>  		const char *arg = argv[i];
> -		if (arg[0] == '-' && arg[1]) {
> +		if (arg[0] == '-' && !strstr(arg, "..")) {

Isn't this way too loose? "--some-opt=I.wish..." would have ".." in it, and we would want to leave room to add new options that may take arbitrary string as an argument.

I would have expected it would be more like
		if (arg[0] == '-' && arg[1] && !starts_with(arg + 1, "..")) {

That is, "anything that begins with '-', if it is to be taken as an option, must not begin with '-..'", which I think should be strict enough.

Show 8 quoted lines
> @@ -2220,6 +2228,7 @@ int setup_revisions(int argc, const char **argv, struct rev_info *revs, struct s
>  				continue;
>  			}
>  
> +
>  			opts = handle_revision_opt(revs, argc - i, argv + i, &left, argv);
>  			if (opts > 0) {
>  				i += opts - 1;
Noise.
Show 9 quoted lines
> @@ -2229,7 +2238,10 @@ int setup_revisions(int argc, const char **argv, struct rev_info *revs, struct s
>  				exit(128);
>  			continue;
>  		}
> -
> +		if (strstr(arg, "..")) {
> +			handle_revision_arg(arg, revs, flags, revarg_opt);
> +			continue;
> +		}

What is this for? We will call handle_revision_arg() whether arg has ".." or not immediately after this one.

>  		if (handle_revision_arg(arg, revs, flags, revarg_opt)) {
>  			int j;
Previous: Kenny Lee Sin CheongNext: Junio C Hamano
Message 4 of 9 in “[GSoC] revision.c: Allow "-" as stand-in for "@{-1}" everywhere a branch is allowed”
  1. 0/2 [GSoC] revision.c: Allow "-" as stand-in for "@{-1}" everywhere a branch is allowedKenny Lee Sin Cheong, Mar 16, 2015
  2. 1/2 "-" and "@{-1}" on various programsKenny Lee Sin Cheong, Mar 16, 2015
  3. 2/2 Add revision range support on "-" and "@{-1}"Kenny Lee Sin Cheong, Mar 16, 2015
  4. Junio C HamanoMar 16, 2015
  5. Junio C HamanoMar 17, 2015
  6. Kenny Lee Sin CheongMar 17, 2015
  7. Junio C HamanoMar 17, 2015
  8. Kenny Lee Sin CheongMar 24, 2015
  9. Junio C HamanoMar 25, 2015

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.