All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: Comments in read-tree about #nALT
Date: Sat, 27 Aug 2005 00:08:17 -0700	[thread overview]
Message-ID: <7vwtm726xq.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0508270151590.23242@iabervon.org> (Daniel Barkalow's message of "Sat, 27 Aug 2005 02:07:17 -0400 (EDT)")

Daniel Barkalow <barkalow@iabervon.org> writes:

> Part of threeway_merge, however, wants to search the rest of the cache for
> interfering entries in some cases, which would have to happen differently,
> because I won't have the cache completely filled out beforehand. I'm
> trying to figure out what the comments are talking about, and they seem to
> refer to a list of the possible cases. Is that list somewhere convenient?

Please look for END_OF_CASE_TABLE in t/t1000-read-tree-m-3way.sh;
the table talks about some of the (ALT) not implemented, but
some of them are ("git whatchanged t/t1000-read-tree-m-3way"
would tell you which).

Two way cases are described in Documentation/git-read-tree.txt,
if you care.  If you were not touching the three-way case right
now, I'd move/copy the three way cases there as well, but that
can wait until after your changes.

  reply	other threads:[~2005-08-27  7:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-27  6:07 Comments in read-tree about #nALT Daniel Barkalow
2005-08-27  7:08 ` Junio C Hamano [this message]
2005-08-27  8:59   ` Junio C Hamano
2005-08-27 21:57   ` Daniel Barkalow
2005-08-27 23:15     ` Daniel Barkalow
2005-08-27 23:35       ` Linus Torvalds
2005-08-28  0:16         ` Daniel Barkalow
2005-08-28  1:18           ` Linus Torvalds
2005-08-30  0:42         ` Junio C Hamano
2005-08-30  0:58           ` Linus Torvalds
2005-08-28  5:45       ` Junio C Hamano
2005-08-28  5:46     ` 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

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

  git send-email \
    --in-reply-to=7vwtm726xq.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=barkalow@iabervon.org \
    --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 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.