From: Andreas Schwab <schwab@linux-m68k.org>
To: shawn wilson <ag4ve.us@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: change symlink
Date: Tue, 30 Oct 2012 22:19:07 +0100 [thread overview]
Message-ID: <m2mwz3odys.fsf@igel.home> (raw)
In-Reply-To: <CAH_OBie-irmpBrJG6KB3W8bgYjQdyVYiUR-SvJPnx1FXUya0uA@mail.gmail.com> (shawn wilson's message of "Tue, 30 Oct 2012 21:07:07 +0000")
shawn wilson <ag4ve.us@gmail.com> writes:
> i'm curious why this is being reported as deleted in status and diff
> and not modified? this was tested on a build of the master branch of
> the current git repo (1.8.0).
>
> mkdir t cd t; git --init
>
> touch test
> git add test
> git commit test -m "test"
>
> ln -s test t2
> git add t2
> git commit t2 -m "symlink"
>
> rm t2
> mkdir -p t2/one
> ln -s test t2/one/test
git add t2/one/test
> this then shows up as:
>
> % git status
> # On branch master
> # Changes not staged for commit:
> # (use "git add/rm <file>..." to update what will be committed)
> # (use "git checkout -- <file>..." to discard changes in working directory)
> #
> # deleted: t2
> #
> no changes added to commit (use "git add" and/or "git commit -a")
I'd expected t2/one/test be reported as untracked.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-10-30 21:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 21:07 change symlink shawn wilson
2012-10-30 21:19 ` Andreas Schwab [this message]
2012-10-30 21:24 ` shawn wilson
2012-10-30 21:35 ` Andreas Schwab
2012-10-30 21:42 ` shawn wilson
2012-10-30 21:50 ` Andreas Schwab
2012-10-30 22:03 ` shawn wilson
2012-10-30 22:09 ` Andreas Schwab
2012-10-30 22:22 ` shawn wilson
2012-10-31 12:05 ` Jeff King
2012-10-31 12:30 ` Jeff King
2012-10-31 13:44 ` Jeff King
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=m2mwz3odys.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=ag4ve.us@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).