Junio C Hamano wrote:
Phil Hord ho...@cisco.com writes:
Do you think '--tree-state' is an acceptable switch or do you have other
suggestions?
I've been calling these 'tokens' myself. A token is a word-or-phrase I
can parse easily with the default $IFS, for simpler script handling.
That
Phil Hord ho...@cisco.com writes:
Consider the usage:
git status # show work-tree status
git status --short # show short work-tree status
git status --tokens # show work-tree status in token form
OK, your --tokens is more about *how* things are output, but it is
unclear how it
Junio C Hamano wrote:
Phil Hord ho...@cisco.com writes:
Consider the usage:
git status # show work-tree status
git status --short # show short work-tree status
git status --tokens # show work-tree status in token form
OK, your --tokens is more about *how* things are output, but
Junio C Hamano gits...@pobox.com writes:
Phil Hord ho...@cisco.com writes:
# tokens and short-status
$ git status --tree --short
## changed-files
M foo.txt
Hrm, how will the existing readers of the output avoid getting
confused by this overloading of ##, which has meant the
Phil Hord wrote:
Junio C Hamano wrote:
Phil Hord ho...@cisco.com writes:
State token strings which may be emitted and their meanings:
merge a merge is in progress
am an am is in progress
am-is-emptythe am patch is empty
rebase
Phil Hord ho...@cisco.com writes:
State token strings which may be emitted and their meanings:
merge a merge is in progress
am an am is in progress
am-is-emptythe am patch is empty
rebase a rebase is in progress
Junio C Hamano wrote:
Phil Hord ho...@cisco.com writes:
State token strings which may be emitted and their meanings:
merge a merge is in progress
am an am is in progress
am-is-emptythe am patch is empty
rebase a rebase is in
7 matches
Mail list logo