git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexei Sholik <alcosholik@gmail.com>
To: git@vger.kernel.org
Subject: 'typechange' in the git-status output
Date: Mon, 14 Mar 2011 20:29:57 +0200	[thread overview]
Message-ID: <AANLkTimWR0avW6mBWGa0ArVB8oZUM7nuvc5AYf=wgU-W@mail.gmail.com> (raw)

Hi git,

I cloned git mirror from github[1]. When I run git-status in it's
working directory, I see no output.

But then, after copying the whole directory with 'cp -r' and running
git-status in the newly created directory, I get the following:

> # 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

git-diff shows

> diff --git a/RelNotes b/RelNotes
> new file mode 100644
> index 0000000..56c3863
> --- /dev/null
> +++ b/RelNotes
> ... // the whole contents of the file

Both copies of the repository are on the branch master with the latest
commit 07873dc. Simply diffing copies of the RelNotes file gives no
output.

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?


  [1]: git://github.com/git/git.git

-- 
Best regards,
Alexei Sholik

             reply	other threads:[~2011-03-14 18:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 18:29 Alexei Sholik [this message]
2011-03-14 18:39 ` 'typechange' in the git-status output Jeff King
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='AANLkTimWR0avW6mBWGa0ArVB8oZUM7nuvc5AYf=wgU-W@mail.gmail.com' \
    --to=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).