Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Dennis Kaarsemaker <dennis@kaarsemaker.net>
Cc: Carlos Pita <carlosjosepita@gmail.com>, git@vger.kernel.org
Subject: Re: [bug] Graph log and orphan branches
Date: Wed, 30 Dec 2015 13:24:40 -0800	[thread overview]
Message-ID: <xmqqa8oreijr.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1451508209.9251.13.camel@kaarsemaker.net> (Dennis Kaarsemaker's message of "Wed, 30 Dec 2015 21:43:29 +0100")

Dennis Kaarsemaker <dennis@kaarsemaker.net> writes:

> On wo, 2015-12-30 at 11:54 -0800, Junio C Hamano wrote:
>> Carlos Pita <carlosjosepita@gmail.com> writes:
>> 
>> > the graph output of log show orphan branches in a way that suggests
>> > they have a parent.
>> 
>> Reminds me of this ancient RFH topic
>> 
>>   http://thread.gmane.org/gmane.comp.version-control.git/236708/focus
>> =239580
>> 
>> which unfortunately got no help...
>
> Instead of a blank line, why not something like this to make root
> commits stand out a bit?
>

That approach will lose information when a root commit is at the
boundary, marked as uninteresting, or on the left/right side of
traversal (when --left-right is requested).  As these pieces of
information that will be lost with such an approach are a lot more
relevant than "have we hit the root?", especially in the majority of
repositories where there is only one root commit, I do not think it
is acceptable.

      parent reply	other threads:[~2015-12-30 21:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 19:46 [bug] Graph log and orphan branches Carlos Pita
2015-12-30 19:48 ` Carlos Pita
2015-12-30 19:54 ` Junio C Hamano
2015-12-30 20:43   ` Dennis Kaarsemaker
2015-12-30 20:46     ` Carlos Pita
2015-12-30 21:24     ` Junio C Hamano [this message]

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

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

  git send-email \
    --in-reply-to=xmqqa8oreijr.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=carlosjosepita@gmail.com \
    --cc=dennis@kaarsemaker.net \
    --cc=git@vger.kernel.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox