From: Junio C Hamano <gitster@pobox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Add "--show-all" revision walker flag for debugging
Date: Sat, 09 Feb 2008 20:21:50 -0800 [thread overview]
Message-ID: <7vd4r54f1d.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <7vy79t4fld.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Sat, 09 Feb 2008 20:09:50 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Linus Torvalds <torvalds@linux-foundation.org> writes:
>
>> The real issue is that it doesn't work. I thought about it, and with
>> multiple roots (which _can_ get merged together) it just isn't something
>> that actually helps.
>>
>> If you couldn't merge across roots, you could have a "uuid+generation
>> header", but the moment you have multiple roots it actually gets quite
>> complex.
>>
>> So scratch the generation header. It's not the answer.
>
> I do not think multiple roots can be helped without going all
> the way down to the roots, and I think it can be proven.
Ah, please scratch that comment. I was puzzled but did not
understand what you meant by uuid+generation.
You are right. If we cannot tell if we are dealing with
disconnected history, we would always need to play safe and do
the clean-up like what I suggested earlier using merge-base
traversal, which could be costly, and we do not want to pay that
penalty in a connected history, which should be the normal case.
Generation header does not help us detect that case, so it is
not useful.
next prev parent reply other threads:[~2008-02-10 4:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 22:02 Add "--show-all" revision walker flag for debugging Linus Torvalds
2008-02-09 23:52 ` Linus Torvalds
2008-02-10 4:44 ` Junio C Hamano
2008-02-10 1:12 ` Johannes Schindelin
2008-02-10 1:22 ` Linus Torvalds
2008-02-10 1:29 ` Johannes Schindelin
2008-02-10 4:09 ` Junio C Hamano
2008-02-10 4:21 ` Junio C Hamano [this message]
2008-02-10 1:28 ` Nicolas Pitre
2008-02-10 1:30 ` Johannes Schindelin
2008-02-10 20:17 ` Jakub Narebski
2008-02-10 20:50 ` Linus Torvalds
2008-02-10 21:04 ` Nicolas Pitre
2008-02-10 22:53 ` Jakub Narebski
2008-02-10 23:11 ` Linus Torvalds
2008-02-11 1:24 ` Jakub Narebski
2008-02-11 1:59 ` Nicolas Pitre
2008-02-11 15:59 ` Linus Torvalds
2008-02-11 16:26 ` Jakub Narebski
2008-02-11 16:39 ` Nicolas Pitre
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=7vd4r54f1d.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.