commit a1839dca295586955508d60963109ea4480afeb8
from: Omar Polo <op@omarpolo.com>
date: Tue Aug 17 10:30:57 2021 UTC

don't include the common commit in log-outgoing

log-outgoing used to include also the latest commit in
REMOTE-LOCATION, and it's misleading (i.e. vc-log-outgoing on a sync'd
repository would still list a commit).

This fixes it by calling next-revision on the remote-location, which
is nil when we're in sync with upstream.

commit - 3ec8a8b420e5adc12df5d291c0679bf9808dc70f
commit + a1839dca295586955508d60963109ea4480afeb8
blob - 4a5d303ebb8b3c20111db133939e062e94db06ba
blob + eb6ac1d1cf1bbe91383a9c4b15f1de9608a94941
--- vc-got.el
+++ vc-got.el
@@ -689,13 +689,14 @@ START-REVISION."
                                limit
                                start-revision)))))
 
-;; XXX: this includes also the latest commit in REMOTE-LOCATION.
 (defun vc-got-log-outgoing (buffer remote-location)
   "Fill BUFFER with the diff between the local worktree branch and REMOTE-LOCATION."
   (vc-setup-buffer buffer)
-  (let ((rl (if (or (not remote-location) (string-empty-p remote-location))
-                (concat "origin/" (vc-got--current-branch))
-              remote-location))
+  (let ((rl (vc-got-next-revision
+             nil
+             (if (or (not remote-location) (string-empty-p remote-location))
+                 (concat "origin/" (vc-got--current-branch))
+               remote-location)))
         (inhibit-read-only t))
     (with-current-buffer buffer
       (vc-got--log nil nil nil rl))))