It give magit the possibility to mimic gitx and gitk log view:
just do C-u l --all RET RET
---
 magit.el   |    4 +++-
 magit.texi |    4 ++++
 2 files changed, 7 insertions(+), 1 deletions(-)

This is a hack, there should be a better solution... But it works!

diff --git a/magit.el b/magit.el
index 2c90133..4caf99d 100644
--- a/magit.el
+++ b/magit.el
@@ -600,7 +600,9 @@ Many Magit faces inherit from this one by default."
        (format "%s from %s to %s" things
                (magit-rev-describe (car range))
                (magit-rev-describe (cdr range)))
-      (format "%s at %s" things (magit-rev-describe (car range))))))
+       (if (string= (car range) "--all")
+           (format "all branches and tags")
+           (format "%s at %s" things (magit-rev-describe (car range)))))))
 
 (defun magit-default-rev ()
   (or (magit-name-rev (magit-commit-at-point t))
diff --git a/magit.texi b/magit.texi
index b7555e5..50d1aec 100644
--- a/magit.texi
+++ b/magit.texi
@@ -328,6 +328,10 @@ Giving a prefix argument to @kbd{l} will ask for the 
starting and end
 point of the history.  This can be used to show the commits that are
 in one branch, but not in another, for example.
 
+As a special case, if you use --all for starting point, and nothing for
+the end point, you will see histories of all branches, as gitx and gitk
+are doing with the same option.
+
 Typing @kbd{L} (or @kbd{C-u L}) will show the log in a more verbose
 form.
 
-- 
1.7.1

Reply via email to