{"thread":{"id":"3299","subject":"[PATCH] allow double click on current HEAD id after git-pull","startedAt":"2006-02-11T11:26:30Z","lastAt":"2006-03-10T01:24:03Z","messageCount":6,"participants":["Olaf Hering","Petr Baudis","Junio C Hamano","Carl Worth","Mark Wooding"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"15914","messageId":"20060211112630.GA12421@suse.de","threadId":"3299","inReplyTo":null,"subject":"[PATCH] allow double click on current HEAD id after git-pull","fromName":"Olaf Hering","fromEmail":"olh@suse.de","sentAt":"2006-02-11T11:26:30Z","receivedAt":"2006-02-11T11:26:30Z","isPatch":true,"sender":{"key":"olh@suse.de","avatar":null},"body":"\nDouble click on to current HEAD commit id is not possible,\nthe dot has to go.\n\nolaf@pomegranate:~/kernel/git/linux-2.6> git-pull\nUnpacking 194 objects\n 100% (194/194) done\n* refs/heads/origin: fast forward to branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6\nUpdating from 5bc159e6cb7ca8d173195919ee935885c129011e to 25bf368b3d98668c5d5f38e2201d8bca16e52680.\nFast forward\n...\nolaf@pomegranate:~/kernel/git/linux-2.6> git-whatchanged 5bc159e6cb7ca8d173195919ee935885c129011e..25bf368b3d98668c5d5f38e2201d8bca16e52680.\nolaf@pomegranate:~/kernel/git/linux-2.6> git-whatchanged 5bc159e6cb7ca8d173195919ee935885c129011e..25bf368b3d98668c5d5f38e2201d8bca16e52680\n<stuff>\n\nIndex: git-1.1.3/git-merge.sh\n===================================================================\n--- git-1.1.3.orig/git-merge.sh\n+++ git-1.1.3/git-merge.sh\n@@ -127,7 +127,7 @@ case \"$#,$common,$no_commit\" in\n \t;;\n 1,\"$head\",*)\n \t# Again the most common case of merging one remote.\n-\techo \"Updating from $head to $1.\"\n+\techo \"Updating from $head to $1\"\n \tgit-update-index --refresh 2>/dev/null\n \tnew_head=$(git-rev-parse --verify \"$1^0\") &&\n \tgit-read-tree -u -m $head \"$new_head\" &&\nIndex: git-1.1.3/git-resolve.sh\n===================================================================\n--- git-1.1.3.orig/git-resolve.sh\n+++ git-1.1.3/git-resolve.sh\n@@ -41,7 +41,7 @@ case \"$common\" in\n \texit 0\n \t;;\n \"$head\")\n-\techo \"Updating from $head to $merge.\"\n+\techo \"Updating from $head to $merge\"\n \tgit-read-tree -u -m $head $merge || exit 1\n \tgit-update-ref HEAD \"$merge\" \"$head\"\n \tgit-diff-tree -p $head $merge | git-apply --stat\n-- \nshort story of a lazy sysadmin:\n alias appserv=wotan\n"},{"id":"17395","messageId":"20060309210250.GY31278@pasky.or.cz","threadId":"3299","inReplyTo":"20060211112630.GA12421@suse.de","subject":"Re: [PATCH] allow double click on current HEAD id after git-pull","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2006-03-09T21:02:50Z","receivedAt":"2006-03-09T21:02:50Z","isPatch":true,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Sat, Feb 11, 2006 at 12:26:30PM CET, I got a letter\nwhere Olaf Hering <olh@suse.de> said that...\n> Double click on to current HEAD commit id is not possible,\n> the dot has to go.\n> \n> olaf@pomegranate:~/kernel/git/linux-2.6> git-pull\n> Unpacking 194 objects\n>  100% (194/194) done\n> * refs/heads/origin: fast forward to branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6\n> Updating from 5bc159e6cb7ca8d173195919ee935885c129011e to 25bf368b3d98668c5d5f38e2201d8bca16e52680.\n                                                                                                    ^\n\nJunio, is there any particular reason why this hasn't been applied?\n\nThanks,\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nOf the 3 great composers Mozart tells us what it's like to be human,\nBeethoven tells us what it's like to be Beethoven and Bach tells us\nwhat it's like to be the universe.  -- Douglas Adams\n"},{"id":"17397","messageId":"7vy7zj2oom.fsf@assigned-by-dhcp.cox.net","threadId":"3299","inReplyTo":"20060309210250.GY31278@pasky.or.cz","subject":"Re: [PATCH] allow double click on current HEAD id after git-pull","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2006-03-09T23:17:29Z","receivedAt":"2006-03-09T23:17:29Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Petr Baudis <pasky@suse.cz> writes:\n\n> Dear diary, on Sat, Feb 11, 2006 at 12:26:30PM CET, I got a letter\n> where Olaf Hering <olh@suse.de> said that...\n>> Double click on to current HEAD commit id is not possible,\n>> the dot has to go.\n>> \n>> olaf@pomegranate:~/kernel/git/linux-2.6> git-pull\n>> Unpacking 194 objects\n>>  100% (194/194) done\n>> * refs/heads/origin: fast forward to branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6\n>> Updating from 5bc159e6cb7ca8d173195919ee935885c129011e to 25bf368b3d98668c5d5f38e2201d8bca16e52680.\n>                                                                                                     ^\n>\n> Junio, is there any particular reason why this hasn't been applied?\n\nWell I kind of like ending a sentence with a full stop.  Isn't\nthis something you can do by confuguiring your cut&paste?\n\nBut I do not have a _very_ strong feeling either way.  If\nmajority of the list wants it that way I do not mind.\n"},{"id":"17399","messageId":"87lkvjxi08.wl%cworth@cworth.org","threadId":"3299","inReplyTo":"7vy7zj2oom.fsf@assigned-by-dhcp.cox.net","subject":"Re: [PATCH] allow double click on current HEAD id after git-pull","fromName":"Carl Worth","fromEmail":"cworth@cworth.org","sentAt":"2006-03-10T00:25:59Z","receivedAt":"2006-03-10T00:25:59Z","isPatch":true,"sender":{"key":"cworth@cworth.org","avatar":"https://gravatar.com/avatar/3746dc28cde609bdbd7f939058356e7e2bbd16d21e32274df0725eb3d998bc5b?d=mp&s=160"},"body":"On Thu, 09 Mar 2006 15:17:29 -0800, Junio C Hamano wrote:\n> Well I kind of like ending a sentence with a full stop.  Isn't\n> this something you can do by confuguiring your cut&paste?\n\nIf the cut-and-paste configuration is limited to just word characters\nvs. word-separating characters, then no. At least not and also\npreserve the ability to select numbers of the form 1.25 .\n\nI don't know if an extra space like the above is good style, but it is\nwhat I have sometimes caught myself doing when ending a sentence with\na URL, for example.\n\n-Carl\n"},{"id":"17401","messageId":"slrne11j9b.fr9.mdw@metalzone.distorted.org.uk","threadId":"3299","inReplyTo":"7vy7zj2oom.fsf@assigned-by-dhcp.cox.net","subject":"Re: [PATCH] allow double click on current HEAD id after git-pull","fromName":"Mark Wooding","fromEmail":"mdw@distorted.org.uk","sentAt":"2006-03-10T00:49:47Z","receivedAt":"2006-03-10T00:49:47Z","isPatch":true,"sender":{"key":"mdw@distorted.org.uk","avatar":null},"body":"Junio C Hamano <junkio@cox.net> wrote:\n\n> Well I kind of like ending a sentence with a full stop.  Isn't\n> this something you can do by confuguiring your cut&paste?\n\nCould do, but since . is a useful filename character it usually seems\nlike a good idea to include it in the set of characters considered a\n`word' by the terminal double-click logic.  I've not used xterm for\nages, but a quick check shows that Eterm isn't smart enough to be told\nthat . followed by a word-constituent is good and should be included in\na word, whereas a trailing . is a different thing which it doesn't want\nto include.\n\nSo I'm in favour of killing the full-stops.  Sorry. :-(\n\n-- [mdw]\n"},{"id":"17403","messageId":"20060310012403.GZ31278@pasky.or.cz","threadId":"3299","inReplyTo":"7vy7zj2oom.fsf@assigned-by-dhcp.cox.net","subject":"Re: [PATCH] allow double click on current HEAD id after git-pull","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2006-03-10T01:24:03Z","receivedAt":"2006-03-10T01:24:03Z","isPatch":true,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Fri, Mar 10, 2006 at 12:17:29AM CET, I got a letter\nwhere Junio C Hamano <junkio@cox.net> said that...\n> Well I kind of like ending a sentence with a full stop.  Isn't\n> this something you can do by confuguiring your cut&paste?\n\nI wouldn't think cut'n'paste is usually that flexible and/or easy to\nconfigure.\n\n> But I do not have a _very_ strong feeling either way.  If\n> majority of the list wants it that way I do not mind.\n\nBeing able to easily cut'n'paste is IMHO an important usability thing,\nand with that long sha1s, who's going to notice a missing fullstop far\nat the right? ;-)\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nOf the 3 great composers Mozart tells us what it's like to be human,\nBeethoven tells us what it's like to be Beethoven and Bach tells us\nwhat it's like to be the universe.  -- Douglas Adams\n"}]}