diff options
author | Owen W. Taylor <otaylor@fishsoup.net> | 2015-02-26 15:46:36 -0500 |
---|---|---|
committer | Owen W. Taylor <otaylor@fishsoup.net> | 2015-02-26 15:49:58 -0500 |
commit | ae1c2a710f43697ad31460044377c3b8a0459bbb (patch) | |
tree | 1725c959403d5218d1d9662c015ae1551d274be1 | |
parent | 89873f9e81bb8b3715e11c6ece190a088d556a28 (diff) | |
download | git-bz-ae1c2a710f43697ad31460044377c3b8a0459bbb.tar.gz |
git bz apply: use consistent ordering of status and description
We ordered status and description differently in the initial display
and in interactive mode. While the two modes are arguably a bit
different in how you are using the information, it's better to use
a consistent ordering so the user can learn where to look.
https://bugzilla.gnome.org/show_bug.cgi?id=678152
-rwxr-xr-x | git-bz | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -1677,13 +1677,13 @@ def do_apply(*args): for patch in bug.patches: if patch.status == 'committed' or patch.status == 'rejected': - print "%d (skipping, %s) - %s" % (patch.attach_id, patch.status, patch.description) + print "%d - %s (skipping, %s)" % (patch.attach_id, patch.description, patch.status) else: patches.append(patch) for patch in patches: if patch.status != 'none': - print "%d (%s) - %s" % (patch.attach_id, patch.status, patch.description) + print "%d - %s (%s)" % (patch.attach_id, patch.description, patch.status) else: print "%d - %s" % (patch.attach_id, patch.description) print |