git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Wincent Colaiuta <win@wincent.com>
To: Teemu Likonen <tlikonen@iki.fi>
Cc: Adam Simpkins <adam@adamsimpkins.net>, git@vger.kernel.org
Subject: Re: log --graph: extra space with --pretty=oneline
Date: Wed, 28 May 2008 13:34:47 +0200	[thread overview]
Message-ID: <D3963BB7-4F3C-4D4F-9423-D03F05100F10@wincent.com> (raw)
In-Reply-To: <20080528112405.GA12065@mithlond.arda.local>

El 28/5/2008, a las 13:24, Teemu Likonen escribió:
> Sometimes "log --graph --pretty=oneline" prints a sort of broken graph
> line. In the git repository try this:
>
> $ git log --graph --pretty=oneline --abbrev-commit -4 8366b7b
>
>
> M   8366b7b... Merge branch 'maint'
> |\
> | M   a2f5be5... Merge branch 'jk/maint-send-email-compose' into maint
> | |\
> | M  \  93c7b9c... Merge branch 'hb/maint-send-email-quote- 
> recipients' into maint
> | |\  |
> | M  \ \  6abf189... Merge branch 'maint-1.5.4' into maint
> | |\  | |
>    ^
>
> Extra spaces there. I don't mind that myself but to some users it may
> look like a bug. Maybe one would expect output like this:
>
>
> M   8366b7b... Merge branch 'maint'
> |\
> | M   a2f5be5... Merge branch 'jk/maint-send-email-compose' into maint
> | |\
> | | \
> | M  \  93c7b9c... Merge branch 'hb/maint-send-email-quote- 
> recipients' into maint
> | |\  \
> | | \  \
> | M  \  |  6abf189... Merge branch 'maint-1.5.4' into maint
> | |\  | |
>
>
> It requires more lines though.

Yes it does, but it definitely looks more readable to me.

W

  reply	other threads:[~2008-05-28 11:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-28 11:24 log --graph: extra space with --pretty=oneline Teemu Likonen
2008-05-28 11:34 ` Wincent Colaiuta [this message]
2008-05-29  8:57 ` Adam Simpkins
2008-05-29  9:03   ` [PATCH] graph API: improve output for merge commits (option 1) Adam Simpkins
2008-05-29  9:04   ` [PATCH] graph API: improve output for merge commits (option 2) Adam Simpkins
2008-05-29 10:25   ` log --graph: extra space with --pretty=oneline Teemu Likonen
2008-06-01 20:56   ` [PATCH 0/2] graph API: improve printing of merges Adam Simpkins
2008-06-01 20:56     ` [PATCH 1/2] graph API: improve display of merge commits Adam Simpkins
2008-06-01 20:56       ` [PATCH 2/2] graph API: avoid printing unnecessary padding before some octopus merges Adam Simpkins
2008-06-01 21:50         ` Junio C Hamano
2008-06-02  0:04           ` Adam Simpkins
2008-06-02  4:41             ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D3963BB7-4F3C-4D4F-9423-D03F05100F10@wincent.com \
    --to=win@wincent.com \
    --cc=adam@adamsimpkins.net \
    --cc=git@vger.kernel.org \
    --cc=tlikonen@iki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).