Thread (11 messages) flat view 11 messages, 4 authors, 2016-06-15

Re: [PATCH] Provide better feedback for the untracked only case in status output

From: Juergen Ruehle <hidden>
Date: 2016-06-15 22:42:48

Possibly related (same subject, not in this thread)

Michael Loeffler writes:
 > hi,
 > 
 > Am Mittwoch, den 10.01.2007, 08:08 +0100 schrieb Juergen Ruehle:
 > ...
 > > @@ -311,12 +312,14 @@ void wt_status_print(struct wt_status *s)
 > ...
 > > +		else if (s->is_initial)
 > > +			printf("nothing to commit (working directory is empty)\n");
 > Shouldn't the user know that there is nothing in his working directory?

:-)

Well this is the state directly after git-init, e.g. the very first
contact with git. Perhaps we should write:

nothing to commit (create files in the working directory and use git add)

 > > +		else
 > > +			printf("nothing to commit (working directory matches HEAD)\n");
 > How about s/matches HEAD/clean/

I like that.

 > There is another thing:
 > # Changed but not added:
 > #   (use "git add <file>..." to incrementally add content to commit)
 > #
 > #       deleted:    blah
 > 
 > How about adding some more hints (e.g.: git rm --cached <file>)
 > depending on the diff_queue in wt_status_print_changed_cb()?

Yes, there's always one more case to consider:-)
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help