From: "Peter Eriksen" <s022018@student.dtu.dk>
To: git@vger.kernel.org
Subject: Re: Tracking few files among many
Date: Sun, 30 Oct 2005 16:52:44 +0100 [thread overview]
Message-ID: <20051030155243.GA28021@ebar091.ebar.dtu.dk> (raw)
In-Reply-To: <4364E6D7.9010707@op5.se>
On Sun, Oct 30, 2005 at 04:29:27PM +0100, Andreas Ericsson wrote:
> Peter Eriksen wrote:
> >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:
...
> OTOH, since you *know* git-status (precisely because it looks for files
> not added to the index) to be slow, you should use git-diff* instead. I
> imagine you know what files you're tracking anyways since it's just a
> subset of 25000-something.
I understand now, I just didn't think about this behavior before.
What I could do is add all my files to .gitignore, but that would
be insane.
Perhaps I was just confused about it calling those files "not tracked".
I know, I know, it was changed recently to this exactly because it
was confusing before.
Thanks for clearing that up for me.
Peter
prev parent reply other threads:[~2005-10-30 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-30 13:00 Tracking few files among many Peter Eriksen
2005-10-30 15:29 ` Andreas Ericsson
2005-10-30 15:52 ` Peter Eriksen [this message]
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=20051030155243.GA28021@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).