From: Junio C Hamano <gitster@pobox.com>
To: "Väinö Järvelä" <v@pp.inet.fi>
Cc: Alex Riesen <raa.lkml@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] Add "--only-untracked" flag to status commands.
Date: Fri, 24 Aug 2007 00:46:02 -0700 [thread overview]
Message-ID: <7v8x81s7d1.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <6D8BA2E0-50CD-4B7B-84D3-3D9A61421131@pp.inet.fi> (Väinö Järvelä's message of "Fri, 24 Aug 2007 09:35:13 +0300")
Väinö Järvelä <v@pp.inet.fi> writes:
> The way I see the flag used is: A user runs "git status", sees that
> there is too much untracked files and not enough scrollback, so he
> runs "git status --only-tracked" to filter the results.
Why?
Just set up .gitignore once then (1) you do not have to worry
about them ever again, and (2) you _will_ still be able to
notice if you accidentally added more cruft, or more
importantly, if you forgot to tell an important file to git.
I think the latter is more important point. If you train a
naive user to use --only-tracked to ignore "Untracked" list, you
are doing him or her a great disservice. Mistake to forget "git
add" a new file before commiting will bound to happen.
next prev parent reply other threads:[~2007-08-24 7:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4fcfda4a654b003f3ae3dc8d56424b5f59f48093.1187897406.git.v@pp.inet.fi>
2007-08-23 19:58 ` [PATCH 1/2] Add "--only-untracked" flag to status commands Väinö Järvelä
2007-08-23 20:50 ` Matthieu Moy
2007-08-24 6:28 ` Väinö Järvelä
[not found] ` <4ec861b086e2d349289f956ea0fe9f4d0559a568.1187897406.git.v@pp.inet.fi>
2007-08-23 19:58 ` [PATCH 2/2] Documented "--only-untracked" flag Väinö Järvelä
2007-08-23 20:32 ` [PATCH 1/2] Add "--only-untracked" flag to status commands Alex Riesen
2007-08-24 6:35 ` Väinö Järvelä
2007-08-24 7:40 ` Jakub Narebski
2007-08-27 13:18 ` Andreas Ericsson
2007-08-24 7:46 ` Junio C Hamano [this message]
2007-08-24 9:31 ` Väinö Järvelä
2007-08-24 9:55 ` Johannes Schindelin
2007-08-24 10:52 ` Väinö Järvelä
2007-08-25 14:39 ` Johannes Schindelin
2007-08-24 11:40 ` Matthieu Moy
2007-08-24 22:47 ` Jakub Narebski
2007-08-24 23:06 ` Junio C Hamano
2007-08-25 6:16 ` Väinö Järvelä
2007-08-25 14:42 ` Johannes Schindelin
2007-08-24 22:33 ` Alex Riesen
2007-08-25 5:37 ` Väinö Järvelä
2007-08-25 6:10 ` 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=7v8x81s7d1.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--cc=v@pp.inet.fi \
/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).