{"thread":{"id":"3462","subject":"[PATCH] git-fetch: print the new and old ref when fast-forwarding","startedAt":"2006-02-25T11:20:13Z","lastAt":"2006-02-25T20:53:32Z","messageCount":3,"participants":["Lukas Sandström","Johannes Schindelin","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"16730","messageId":"44003D6D.2010406@etek.chalmers.se","threadId":"3462","inReplyTo":null,"subject":"[PATCH] git-fetch: print the new and old ref when fast-forwarding","fromName":"Lukas Sandström","fromEmail":"lukass@etek.chalmers.se","sentAt":"2006-02-25T11:20:13Z","receivedAt":"2006-02-25T11:20:13Z","isPatch":true,"sender":{"key":"luksan@gmail.com","avatar":"https://avatars.githubusercontent.com/u/152281?v=4"},"body":"Signed-off-by: Lukas Sandström <lukass@etek.chalmers.se>\n\n---\nThis is useful when you check out new changes with gitk.\nJust copy/paste the old ref into gitk from the terminal.\n\n git-fetch.sh |    1 +\n 1 files changed, 1 insertions(+), 0 deletions(-)\n\n78f2844c17bb8627e84389e3026906d074c43363\ndiff --git a/git-fetch.sh b/git-fetch.sh\nindex fcc24f8..a3e2a34 100755\n--- a/git-fetch.sh\n+++ b/git-fetch.sh\n@@ -164,6 +164,7 @@ fast_forward_local () {\n \t\t;;\n \t    *,$local)\n \t\techo >&2 \"* $1: fast forward to $3\"\n+\t\techo >&2 \"  from $local to $2\"\n \t\tgit-update-ref \"$1\" \"$2\" \"$local\"\n \t\t;;\n \t    *)\n-- \n1.2.3.gc412\n"},{"id":"16732","messageId":"Pine.LNX.4.63.0602252107110.17999@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"3462","inReplyTo":"44003D6D.2010406@etek.chalmers.se","subject":"Re: [PATCH] git-fetch: print the new and old ref when fast-forwarding","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2006-02-25T20:08:37Z","receivedAt":"2006-02-25T20:08:37Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 25 Feb 2006, Lukas Sandström wrote:\n\n> This is useful when you check out new changes with gitk.\n> Just copy/paste the old ref into gitk from the terminal.\n\nWhy does \"gitk ORIG_HEAD..HEAD\" not work? (It also does the correct thing \nwhen pulling...)\n\nHth,\nDscho\n"},{"id":"16733","messageId":"7vlkvz6tyr.fsf@assigned-by-dhcp.cox.net","threadId":"3462","inReplyTo":"Pine.LNX.4.63.0602252107110.17999@wbgn013.biozentrum.uni-wuerzburg.de","subject":"Re: [PATCH] git-fetch: print the new and old ref when fast-forwarding","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-02-25T20:53:32Z","receivedAt":"2006-02-25T20:53:32Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:\n\n>> This is useful when you check out new changes with gitk.\n>> Just copy/paste the old ref into gitk from the terminal.\n>\n> Why does \"gitk ORIG_HEAD..HEAD\" not work? (It also does the correct thing \n> when pulling...)\n\nFor most projects and repositories with single interesting head,\nthat would work just fine.\n\nIf you use additional Pull: lines to track more than one remote\nrefs, this patch would help.\n\nFor example, if you are tracking my \"next\" while keeping an eye\non my \"master\" and \"pu\", your .git/remotes/origin file may have\nsomething like this:\n\n\tURL: git://git.kernel.org/pub/scm/git/git.git\n        Pull: next:origin\n        Pull: master:ko-master\n        Pull: pu:ko-pu\n\nWhen \"git pull origin\" pulls my next branch into your current\nbranch (typically \"master\"), it also fast forwards your tracking\nbranches ko-master and ko-pu.  If you want to see what I merged\nin the meantime, you would want to get the old value of\nko-master and the new value and feed them to gitk (or git log).\nORIG_HEAD in this case was the old value of _your_ current\nbranch head, and is not useful to see what happened to my master\nbranch.\n"}]}