From: Christian Biesinger <cbiesinger@web.de>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] So... are people happy with commit/status -v?
Date: Sun, 19 Feb 2006 16:18:59 +0100 [thread overview]
Message-ID: <43F88C63.3020100@web.de> (raw)
In-Reply-To: <7vvevhj6x4.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> I usually never do commits from a subdirectory, also I rarely do
> partial commits, so this is not a big issue to me, but are
> people happy with the current commit/status?
The part that annoyed me most was that "git-status --only ." completely
ignores the specified path and tells me about the whole tree, rather
than just the current directory and subdirectories. While I think I'd
prefer it if the commands limited themselves to the current directory by
default, I don't mind the current behaviour, as long as I still have the
possibility to limit to the subdirectory.
prev parent reply other threads:[~2006-02-19 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 9:41 [RFC] So... are people happy with commit/status -v? Junio C Hamano
2006-02-19 15:18 ` Christian Biesinger [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=43F88C63.3020100@web.de \
--to=cbiesinger@web.de \
--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).