From: "Peter Eriksen" <s022018@student.dtu.dk>
To: git@vger.kernel.org
Subject: Tracking few files among many
Date: Sun, 30 Oct 2005 14:00:02 +0100 [thread overview]
Message-ID: <20051030130001.GA26652@ebar091.ebar.dtu.dk> (raw)
Hello,
There's something I can't figure out. I'm tracking a few
configuration files in $HOME, but some operations are really
slow. Let's take git-status as example:
~ > git-status >laaangsom.txt
~ > wc -l laaangsom.txt
25875 laaangsom.txt
~ > cat laaangsom.txt
#
# Changed but not updated:
# (use git-update-index to mark for commit)
#
# modified: .gaim/blist.xml
# modified: .gaim/prefs.xml
# modified: .mozilla/firefox/s4q22693.default/prefs.js
#
#
# Untracked files:
# (use "git add" to add to commit)
#
# [ A lot of untracked files. See the line count above. ]
What is going on? This really doesn't seem like the wanted
behavior. Have I missed something? I'm using
46774a81f9d6ca4d230d33757afe9dd07bfe398b (GIT 0.99.9).
Regards,
Peter
next reply other threads:[~2005-10-30 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 13:00 Peter Eriksen [this message]
2005-10-30 15:29 ` Tracking few files among many Andreas Ericsson
2005-10-30 15:52 ` Peter Eriksen
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=20051030130001.GA26652@ebar091.ebar.dtu.dk \
--to=s022018@student.dtu.dk \
--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).