From: Jeff King <peff@peff.net>
To: Alexei Sholik <alcosholik@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: 'typechange' in the git-status output
Date: Mon, 14 Mar 2011 14:39:48 -0400 [thread overview]
Message-ID: <20110314183947.GA21070@sigill.intra.peff.net> (raw)
In-Reply-To: <AANLkTimWR0avW6mBWGa0ArVB8oZUM7nuvc5AYf=wgU-W@mail.gmail.com>
On Mon, Mar 14, 2011 at 08:29:57PM +0200, Alexei Sholik wrote:
> But then, after copying the whole directory with 'cp -r' and running
> git-status in the newly created directory, I get the following:
"cp -r" isn't an exact copy. You probably want "cp -a" or at least "cp
-rs".
> > # On branch master
> > # Changed but not updated:
> > # (use "git add <file>..." to update what will be committed)
> > # (use "git checkout -- <file>..." to discard changes in working directory)
> > #
> > # typechange: RelNotes
Right. RelNotes is a symlink. But "cp -r" dereferences the symlink and
copies the file contents themselves.
> What happened with the copied repository? I've found a couple of
> instances of the word 'typechange' in the source, but no mention in
> the docs. What does it mean and what could be the cause of this
> change?
It's the same as the "T" flag in "git diff --name-status". Namely, the
type of the file changed (between a symlink and a regular file).
-Peff
next prev parent reply other threads:[~2011-03-14 18:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 18:29 'typechange' in the git-status output Alexei Sholik
2011-03-14 18:39 ` Jeff King [this message]
2011-03-14 18:39 ` Alexei Sholik
2011-03-14 18:59 ` Drew Northup
2011-03-14 19:22 ` Jonathan Nieder
2011-03-14 19:27 ` Jeff King
2011-03-14 19:44 ` 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=20110314183947.GA21070@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=alcosholik@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).