Phil Hord ho...@cisco.com writes:
+ if (state-substate==WT_SUBSTATE_NOMINAL)
status_printf_ln(s, color,
_(The current patch is empty.));
This looks weird. First, spaces around == (here and below). Then, the
logic is unintuitive. The if suggests everything is
Phil Hord ho...@cisco.com writes:
+ merge a git-merge is in progress
+ am a git-am is in progress
+ rebase a git-rebase is in progress
+ rebase-interactive a git-rebase--interactive is in progress
+ cherry-picka
Matthieu Moy wrote:
Phil Hord ho...@cisco.com writes:
+merge a git-merge is in progress
+am a git-am is in progress
+rebase a git-rebase is in progress
+rebase-interactive a git-rebase--interactive is in progress
+cherry-pick
Recently git-status learned to display the state of the git
sequencer in long form to help the user remember an interrupted
command. This information is also useful in short form to
humans and scripts, but no option is available to boil it down.
Teach git-status to report the sequencer state in
Recently git-status learned to display the state of the git
sequencer in long form to help the user remember an interrupted
command. This information is also useful in short form to
humans and scripts, but no option is available to boil it down.
Teach git-status to report the sequencer state in
5 matches
Mail list logo
