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

Re: [PATCH] Fix `git rev-list --show-notes HEAD` when there are no notes

From
Jeff King <peff@peff.net>
Date
Aug 23, 2015, 17:43 UTC
Message-ID
<20150823174309.GA24735@sigill.intra.peff.net>
In-Reply-To
<0LZlZ2-1Z1Zyn1mzk-00lZ3Z@mail.gmx.com>
On Sat, Aug 22, 2015 at 05:14:39PM +0200, Johannes Schindelin wrote:
Show 8 quoted lines
> The `format_display_notes()` function clearly assumes that the data
> structure holding the notes has been initialized already, i.e. that the
> `display_notes_trees` variable is no longer `NULL`.
> 
> However, when there are no notes whatsoever, this variable is still
> `NULL`, even after initialization.
> 
> So let's be graceful and just return if that data structure is `NULL`.

Hrm. This is supposed to be made non-NULL by calling init_display_notes. The "git-log" code does this properly, and can show notes. The "rev-list" code does not, and hits this assert. But that also means that it cannot actually _show_ notes, and your patch is papering over the problem.

I would think we would need something more like this:
diff --git a/builtin/rev-list.c b/builtin/rev-list.c
index ff84a82..fc73a6f 100644
--- a/builtin/rev-list.c
+++ b/builtin/rev-list.c
@@ -279,6 +279,7 @@ int cmd_rev_list(int argc, const char **argv, const char *prefix)
 	int bisect_show_vars = 0;
 	int bisect_find_all = 0;
 	int use_bitmap_index = 0;
+	struct userformat_want w;
 
 	git_config(git_default_config, NULL);
 	init_revisions(&revs, prefix);
@@ -349,6 +350,14 @@ int cmd_rev_list(int argc, const char **argv, const char *prefix)
 	    revs.diff)
 		usage(rev_list_usage);
 
+	memset(&w, 0, sizeof(w));
+	userformat_find_requirements(NULL, &w);
+
+	if (!revs.show_notes_given && w.notes)
+		revs.show_notes = 1;
+	if (revs.show_notes)
+		init_display_notes(&revs.notes_opt);
+
 	save_commit_buffer = (revs.verbose_header ||
 			      revs.grep_filter.pattern_list ||
 			      revs.grep_filter.header_list);

but it looks like that is not enough to convince the pretty-printer to
actually show notes (I suspect we need something like the
pretty_ctx->notes_message setup that is in show_log()).

I don't know how deeply anybody _cares_ about showing notes via
rev-list. It has clearly never worked. But rather than silently
accepting --show-notes (and not showing any notes!), perhaps we should
tell the user that it does not work. Likewise, the "%N" --format
specifier never expands in rev-list, and should probably be removed from
the rev-list documentation.

Although...

> Reported in https://github.com/msysgit/git/issues/363.

After reading your subject, I wondered why "git rev-list --show-notes
HEAD" did not crash for me (whether or not I had notes). But the key
element from that issue is the addition of "--grep", which is what
triggers us to actually look at the notes (since rev-list otherwise does
not support displaying them). And that _does_ work with my patch above.
So perhaps that is useful, though again, it has never worked in the
past (and with your patch, it would silently return no results, whether
the grep matched or not).

Of course it's a terrible interface to make "--show-notes --grep" grep
the notes, but not actually _show_ them. :-/

> diff --git a/notes.c b/notes.c
> index df08209..24a335a 100644
> --- a/notes.c
> +++ b/notes.c
> @@ -1266,7 +1266,10 @@ void format_display_notes(const unsigned char *object_sha1,
>  			  struct strbuf *sb, const char *output_encoding, int raw)
>  {
>  	int i;
> -	assert(display_notes_trees);
> +
> +	if (!display_notes_trees)
> +		return;
> +

So I'm not really in favor of this approach, but if we do go that route,
the comment above the declaration of format_display_notes needs to be
updated.

-Peff
Previous: Johan HerlandNext: Jeff King
Message 3 of 7 in “Fix `git rev-list --show-notes HEAD` when there are no notes”
  1. Fix `git rev-list --show-notes HEAD` when there are no notesJohannes Schindelin, Aug 22, 2015
  2. Johan HerlandAug 22, 2015
  3. Jeff KingAug 23, 2015
  4. rev-list: make it obvious that we do not support notesJeff King, Aug 23, 2015
  5. Johannes SchindelinAug 24, 2015
  6. Jeff KingAug 24, 2015
  7. Johannes SchindelinAug 24, 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.