From: Fredrik Kuivinen <freku045@student.liu.se>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: What's new in git.git master branch
Date: Thu, 1 Dec 2005 09:54:33 +0100 [thread overview]
Message-ID: <20051201085433.GA7866@c165.ib.student.liu.se> (raw)
In-Reply-To: <7vlkz5n3r1.fsf@assigned-by-dhcp.cox.net>
On Wed, Nov 30, 2005 at 02:57:06PM -0800, Junio C Hamano wrote:
[...]
> - ls-tree rewrite (Linus).
[...]
> One interesting change is ls-tree rewrite by Linus. The command
> does _not_ show tree nodes when running with -r flag anymore.
> Running "git diff v0.99.9i t/t3100-ls-tree-restrict.sh"
> after updating to the master tells you the summary of changes in
> the behaviour.
It turns out that this change breaks the directory/file conflict
handling in git-merge-recursive. Right now merge-recursive uses
git-ls-tree -r -z <tree SHA1>
to get a listing of every blob object (which corresponds to files) and
every tree object (which corresponds to directories) in the tree
designated by the SHA1. With the new ls-tree behaviour we don't get
any tree objects and hence merge-recursive can't do the d/f conflict
detection as it doesn't know about the directories. As we don't track
empty directories it could be fixed within git-merge-recursive, a list
of the directory names can be obtained from the list of file names by
stripping everything after the last slash in the file names.
Should we do it that way or should ls-tree be changed?
- Fredrik
next prev parent reply other threads:[~2005-12-01 8:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-30 22:57 What's new in git.git master branch Junio C Hamano
2005-12-01 8:54 ` Fredrik Kuivinen [this message]
2005-12-01 9:38 ` Junio C Hamano
2005-12-02 5:45 ` Junio C Hamano
2005-12-02 5:46 ` Junio C Hamano
2005-12-02 8:46 ` Fredrik Kuivinen
2005-12-02 8:36 ` Fredrik Kuivinen
2005-12-07 10:01 ` [PATCH 3/3] update-index: allow --index-info to add higher stages Junio C Hamano
2005-12-01 18:35 ` git-ls-tree: add "-t" option to always show the tree entries Linus Torvalds
2005-12-01 21:15 ` Junio C Hamano
2005-12-01 21:57 ` Linus Torvalds
2005-12-01 22:04 ` Junio C Hamano
2005-12-01 22:56 ` [PATCH] ls-tree: --name-only Junio C Hamano
2005-12-02 22:12 ` git-ls-tree: add "-t" option to always show the tree entries Junio C Hamano
2005-12-02 23:11 ` Linus Torvalds
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=20051201085433.GA7866@c165.ib.student.liu.se \
--to=freku045@student.liu.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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