From: Johannes Sixt <j.sixt@viscovery.net>
To: Robin Rosenberg <robin.rosenberg@dewire.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] RFC Optionally handle symbolic links as copies
Date: Thu, 06 Dec 2012 07:59:33 +0100 [thread overview]
Message-ID: <50C04255.8050209@viscovery.net> (raw)
In-Reply-To: <1354747575-89277-1-git-send-email-robin.rosenberg@dewire.com>
Am 12/5/2012 23:46, schrieb Robin Rosenberg:
> - git status - when do we report a diff.
> - After checkout we should probably not
Are you saying that it should be ignored that the index records a symbolic
link, but the worktree contains a regular file and that the regular file
does not even contain the value of the symbolic link (like it would in the
core.symlinks=false case)?
-- Hannes
next prev parent reply other threads:[~2012-12-06 6:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 22:46 [PATCH] RFC Optionally handle symbolic links as copies Robin Rosenberg
2012-12-05 23:51 ` Junio C Hamano
2012-12-06 1:23 ` Robin Rosenberg
2012-12-12 14:43 ` Michael J Gruber
2012-12-12 16:15 ` Robin Rosenberg
2012-12-12 20:22 ` Junio C Hamano
2012-12-06 6:59 ` Johannes Sixt [this message]
2012-12-06 11:51 ` Robin Rosenberg
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=50C04255.8050209@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=robin.rosenberg@dewire.com \
/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;
as well as URLs for NNTP newsgroup(s).