From: Yasushi SHOJI <yashi@atmark-techno.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git status: print files under untracked dir if -a is given
Date: Tue, 30 May 2006 21:55:16 +0900 [thread overview]
Message-ID: <87r72bd64r.wl@mail2.atmark-techno.com> (raw)
In-Reply-To: <7vfyir26v4.fsf@assigned-by-dhcp.cox.net>
Hi Junio,
At Tue, 30 May 2006 02:34:55 -0700,
Junio C Hamano wrote:
>
> Yasushi SHOJI <yashi@atmark-techno.com> writes:
>
> > git status: print files under untracked dir if -a is given
> >
> > git status (git-commit.sh) currently doesn't show files under
> > untracked directory. this is inconvenient when adding many files
> > under new directory.
> >
> > this patch change its behavior to show files under untracked directory
> > if option --all is given.
> >
> > Signed-off-by: Yasushi SHOJI <yashi@atmark-techno.com>
>
> I do not quite understand your rationale behind linking -a and
> "show untracked" behaviour. In many cases, after modifying
> multiple files "commit -a" is the preferred way to make commits
> for people who keep their tree clean (meaning, they do not leave
> unrelated changes to their working tree files), and I suspect
> your change would clutter their commit log buffer with unrelated
> files they did not ask to see.
I assumed "--all" to mean "every single file under a working dir
except ignored". so I thought users of "commit -a" wouldn't mind to
see files under untracked dir.
but I was wrong. man page clearly states that "... new files you have
not told git about are not affected."
# I admit I haven't used -a with commit because of my
# misunderstanding. it's nice to know the option is much safer than I
# expected.
> At least this would make things somewhat unpleasant for me to
> use, since I do "commit -a" often and I have my random notes
> files under ./+trash subdirectory of the main project (yes, I
> know I could add /+trash to .gitignore).
I wasn't expecting that usage.
> We have something different but perhaps related by Matthias
> Lederhofer to add "git status --untracked" since you did this
> patch.
>
> commit 443f8338b9e248353a7095a1096684f1ed106c66
> Author: Matthias Lederhofer <matled@gmx.net>
> Date: Mon May 22 23:02:06 2006 +0200
>
> Does it solve your problem?
yes, it perfectly does.
thanks,
--
yashi
prev parent reply other threads:[~2006-05-30 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 8:46 [PATCH] git status: print files under untracked dir if -a is given Yasushi SHOJI
2006-05-30 9:34 ` Junio C Hamano
2006-05-30 12:55 ` Yasushi SHOJI [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=87r72bd64r.wl@mail2.atmark-techno.com \
--to=yashi@atmark-techno.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).