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

Re: [PATCH] log: make --abbrev-commit's ellipsis configurable

From
Thomas Rast <trast@student.ethz.ch>
Date
Feb 13, 2009, 13:37 UTC
Message-ID
<200902131437.49293.trast@student.ethz.ch>
In-Reply-To
<alpine.DEB.1.00.0902131418230.10279@pacific.mpi-cbg.de>
Johannes Schindelin wrote:
> On Fri, 13 Feb 2009, Thomas Rast wrote:
[...]
Show 9 quoted lines
> >  log-tree.c               |   19 ++++++++++++++-----
> >  log-tree.h               |    3 +++
> 
> I am slightly worried that you overshoot here, as log-tree.c has plumbing 
> users, too, no?
> 
> How about making this an option, and passing it in rev_opts instead?  This 
> option could then be defaulted to in git-log, when the user said 
> --abbrev-commit.

But the 'git_config(git_log_config, NULL);' that sets the new variable to false is only called from cmd_{log,show,whatchanged,reflog}. I should have indicated this in the commit messaged, sorry.

The real problem with stuffing it in rev_opts (actually rev_info :-) is that it seems inconsistent to not change the 'Merge: blah' line's format. But that is generated in pretty.c, in add_merge_info via pp_header from pretty_print_commit, which has a bunch of users in various 'builtin-*.c'.

So do I sacrifice symmetry (abbrev_commit is indeed stored in rev_info), or touch the other ~7 users of pretty_print_commit too?

-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Johannes SchindelinNext: Johannes Schindelin
Message 3 of 11 in “log: make --abbrev-commit's ellipsis configurable”
  1. log: make --abbrev-commit's ellipsis configurableThomas Rast, Feb 13, 2009
  2. Johannes SchindelinFeb 13, 2009
  3. Thomas RastFeb 13, 2009
  4. Johannes SchindelinFeb 13, 2009
  5. log: make --abbrev-commit's ellipsis configurableThomas Rast, Feb 13, 2009
  6. Johannes SixtFeb 13, 2009
  7. Jeff KingFeb 13, 2009
  8. Junio C HamanoFeb 13, 2009
  9. log: do not print ellipses with --abbrev-commitThomas Rast, Feb 13, 2009
  10. Jeff KingFeb 13, 2009
  11. Jakub NarebskiFeb 13, 2009

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.