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

Re: [PATCH v4 2/2] log: add --show-linear-break to help see non-linear history

From
Junio C Hamano <gitster@pobox.com>
Date
Mar 25, 2014, 22:30 UTC
Message-ID
<xmqqr45pkj1o.fsf@gitster.dls.corp.google.com>
In-Reply-To
<1395753807-23228-2-git-send-email-pclouds@gmail.com>
Nguyễn Thái Ngọc Duy  <pclouds@gmail.com> writes:
Show 34 quoted lines
> Option explanation is in rev-list-options.txt. The interaction with -z
> is left undecided.
>
> Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
> ---
>  On Fri, Mar 21, 2014 at 2:15 AM, Junio C Hamano <gitster@pobox.com> wrote:
>  >>  * Get rid of saved_linear, use another flag in struct object instead
>  >
>  > I cannot offhand say if I like this change or not.  A flag bit is a
>  > scarce and limited resource; commit slabs felt more suited for
>  > implementation of corner case eye-candies.
>
>  I leave it in bit 26. We can move it out when we run low on flag bits.
>
>  >>  * Fix not showing the break bar after a root commit if the dag graph
>  >>    has multiple roots
>  >
>  > I definitely do not like the way a commit-list data structure is
>  > abused to hold a phoney element that points at a NULL with its item
>  > pointer.  Allocate a single bit in revs that says "I haven't done
>  > anything yet" if you want to catch the "first-ness" without breaking
>  > what commit_list_insert() and friends are expecting to see---they
>  > never expect to see a NULL asked to be on the list, AFAIK.
>
>  Fixed.
>
>  >>  * Make it work with --graph (although I don't really see the point of
>  >>    using both at the same time)
>  >
>  > I do not see the point, either.  I vaguely recall that the previous
>  > iteration refused the combination at the option parser level, which
>  > I think would be the right thing to do.
>
>  Fixed.
All changes look good to me.

Especially on the last one because the new "printf()" calls do not even attempt to call into the graph API to tell it that it created a gutter above or give it a chance to draw all vertical lines to connect the graph part.

Will replace and advance them to "Will merge to 'next'" state.
Thanks.
Previous: Nguyễn Thái Ngọc Duy
Message 19 of 19 in “Confusing git log --- First time bug submission please advise on best practices”
  1. Francis StephensFeb 6, 2014
  2. Vincent van RavesteijnFeb 6, 2014
  3. David KastrupFeb 6, 2014
  4. Francis StephensFeb 7, 2014
  5. Duy NguyenFeb 7, 2014
  6. demerphqFeb 7, 2014
  7. log: add --show-linear-break to help see non-linear historyNguyễn Thái Ngọc Duy, Feb 8, 2014
  8. log: add --nonlinear-barrier to help see non-linear historyNguyễn Thái Ngọc Duy, Mar 17, 2014
  9. Eric SunshineMar 17, 2014
  10. Junio C HamanoMar 17, 2014
  11. Duy NguyenMar 18, 2014
  12. Junio C HamanoMar 18, 2014
  13. 1/2 object.h: centralize object flag allocationNguyễn Thái Ngọc Duy, Mar 20, 2014
  14. 2/2 log: add --show-linear-break to help see non-linear historyNguyễn Thái Ngọc Duy, Mar 20, 2014
  15. Junio C HamanoMar 20, 2014
  16. Duy NguyenMar 21, 2014
  17. 1/2 object.h: centralize object flag allocationNguyễn Thái Ngọc Duy, Mar 25, 2014
  18. 2/2 log: add --show-linear-break to help see non-linear historyNguyễn Thái Ngọc Duy, Mar 25, 2014
  19. Junio C HamanoMar 25, 2014

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.