Subject: Re: [PATCH 0/2] Log pretty format alignment improvements

From: Junio C Hamano <[email-masked]>
Date: Fri, 17 Jun 2016 09:43:15 -0700

Duy Nguyen <[email-masked]> writes:

> Ah ok. This command with this series (using %>(n))
>
> ~/w/git/git log --format='%>(50,trunc)%s' --graph -15 origin/pu
>
> and the system one at version 2.7.3 (using %>|(n))
>
> /usr/bin/git log --format='%>|(50,trunc)%s' --graph -15 origin/pu
>
> both produce the same output like this, checked with md5sum
>
> *   Merge branch 'js/am-3-merge-recursive-direct' in..
> |\  
> | *          am: make a direct call to merge_recursive
> | * merge_recursive_options: introduce the "gently" ..
> * |            Merge branch 'tb/complete-status' into pu
> |\ \  
> | * |                         completion: add git status
> | * |      completion: add __git_get_option_value helper
> | * | completion: factor out untracked file modes into..
> * | |    Merge branch 'mj/log-show-signature-conf' into pu
> |\ \ \  
> | * | |    log: "--no-show-signature" commmand-line option
> | * | | log: add "log.showsignature" configuration varia..
> * | | |              Merge branch 'nd/worktree-lock' into pu
> |\ \ \ \  
> | * | | |  worktree.c: find_worktree() search by path suffix
> | * | | |                     worktree: add "unlock" command
> | * | | |                       worktree: add "lock" command
> | * | | |               worktree.c: add is_worktree_locked()
>
> The output looks weird though, which makes me a bit hesitate to add it
> in the test suite...

It may become easier to see if you used %<(N) vs %<|(N) instead?