From: Juergen Ruehle <j.ruehle@bmiag.de>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: [PATCH/RFC] Assorted small changes to runstatus
Date: Tue, 2 Jan 2007 20:26:19 +0100 [thread overview]
Message-ID: <1167765983316-git-send-email-j.ruehle@bmiag.de> (raw)
As a regular user of git-status I'd like to propose some small changes and a
fix:
- wording changes to the section headers
- more context awareness in the nothing-to-commit line
- fix runstatus breakage when amending a root commit
Additional Notes:
- if git-reset <commit> <path> provided the ability to remove path from the
index (if not present in commit) runstatus could advertise reset as the
universal unstaging tool (in the non-initial-commit case)
(this is similar to the recent request on the list to allow
git-commit -o <path> to commit removal of path)
- IMO git-rm without -f should not remove anything if HEAD doesn't exist
(i.e. from the initial commit); this might be a bug
next reply other threads:[~2007-01-02 19:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 19:26 Juergen Ruehle [this message]
2007-01-02 19:26 ` [PATCH 1/4] Clarify syntax and role of git-add in status output Juergen Ruehle
2007-01-02 19:26 ` [PATCH 2/4] Improve cached content header of " Juergen Ruehle
2007-01-05 10:54 ` Andy Whitcroft
2007-01-05 11:22 ` Junio C Hamano
2007-01-05 13:14 ` Andy Whitcroft
2007-01-05 17:14 ` Juergen Ruehle
2007-01-05 18:42 ` Junio C Hamano
2007-01-08 13:28 ` Andy Whitcroft
2007-01-08 14:27 ` Juergen Ruehle
2007-01-02 19:26 ` [PATCH 3/4] Improve "nothing to commit" part " Juergen Ruehle
2007-01-02 19:26 ` [PATCH 4/4] Support --amend on initial commit in " Juergen Ruehle
2007-01-03 2:51 ` [PATCH/RFC] Assorted small changes to runstatus Junio C Hamano
2007-01-03 5:34 ` Juergen Ruehle
2007-01-07 19:18 ` [PATCH] Remove unnecessary git-rm --cached reference from status output Juergen Ruehle
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=1167765983316-git-send-email-j.ruehle@bmiag.de \
--to=j.ruehle@bmiag.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).