{"thread":{"id":"3574","subject":"any problems with new branch of gitk?","startedAt":"2006-03-05T22:09:17Z","lastAt":"2006-03-15T13:00:28Z","messageCount":5,"participants":["Paul Mackerras","A Large Angry SCM","Alex Riesen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"17205","messageId":"17419.24973.402408.237865@cargo.ozlabs.ibm.com","threadId":"3574","inReplyTo":null,"subject":"any problems with new branch of gitk?","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2006-03-05T22:09:17Z","receivedAt":"2006-03-05T22:09:17Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"I'm planning to pull the `new' branch of the gitk repository into the\nmaster branch, making the new version of gitk the standard version\nthat will go into the git.git repository.  As far as I know the new\nversion does everything the old version does.  Does anyone know of any\nproblems with the new gitk that weren't in the old one?\n\nThanks,\nPaul.\n"},{"id":"17209","messageId":"440B7136.2000809@gmail.com","threadId":"3574","inReplyTo":"17419.24973.402408.237865@cargo.ozlabs.ibm.com","subject":"Re: any problems with new branch of gitk?","fromName":"A Large Angry SCM","fromEmail":"gitzilla@gmail.com","sentAt":"2006-03-05T23:16:06Z","receivedAt":"2006-03-05T23:16:06Z","isPatch":false,"sender":{"key":"gitzilla@gmail.com","avatar":"https://gravatar.com/avatar/354625c442439908ff3dd99757dee330e29e9df7847472384faf7a00add247fb?d=mp&s=160"},"body":"Paul Mackerras wrote:\n> I'm planning to pull the `new' branch of the gitk repository into the\n> master branch, making the new version of gitk the standard version\n> that will go into the git.git repository.  As far as I know the new\n> version does everything the old version does.  Does anyone know of any\n> problems with the new gitk that weren't in the old one?\n\nI don't know if the old version has this problem but the new version \ndoes not have a \"busy\" pointer while it's waiting for a merge diff. Take \na look at the ACPI mega(octo)pus merge that happened in January.\n"},{"id":"17263","messageId":"20060306202340.GA5946@steel.home","threadId":"3574","inReplyTo":"17419.24973.402408.237865@cargo.ozlabs.ibm.com","subject":"Re: any problems with new branch of gitk?","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2006-03-06T20:23:40Z","receivedAt":"2006-03-06T20:23:40Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"Paul Mackerras, Sun, Mar 05, 2006 23:09:17 +0100:\n> I'm planning to pull the `new' branch of the gitk repository into the\n> master branch, making the new version of gitk the standard version\n> that will go into the git.git repository.  As far as I know the new\n> version does everything the old version does.  Does anyone know of any\n> problems with the new gitk that weren't in the old one?\n\nI don't if that was intended (see the screenshot attached), but some\nlines miss arrows. Click on where the arrow would be works (jump to\ncounterpart arrow). Never have this with the old gitk.\n\nTcl/Tk 8.4.9 (Gentoo).\n\n"},{"id":"17560","messageId":"17431.63509.670409.212654@cargo.ozlabs.ibm.com","threadId":"3574","inReplyTo":"20060306202340.GA5946@steel.home","subject":"Re: any problems with new branch of gitk?","fromName":"Paul Mackerras","fromEmail":"paulus@samba.org","sentAt":"2006-03-15T11:18:45Z","receivedAt":"2006-03-15T11:18:45Z","isPatch":false,"sender":{"key":"paulus@samba.org","avatar":"https://avatars.githubusercontent.com/u/1606439?v=4"},"body":"Alex Riesen writes:\n\n> I don't if that was intended (see the screenshot attached), but some\n> lines miss arrows. Click on where the arrow would be works (jump to\n> counterpart arrow). Never have this with the old gitk.\n> \n> Tcl/Tk 8.4.9 (Gentoo).\n\nYes, it seems that tk 8.4 can't draw arrows on the ends of diagonal\nline segments.  The old gitk coped with this by simply shortening the\nline until it got to a vertical line segment.  I can probably do\nbetter than that with the new layout algorithm.  I'll look at it.\n\nPaul.\n"},{"id":"17561","messageId":"81b0412b0603150500k11e69c5s95158b61fda3ca70@mail.gmail.com","threadId":"3574","inReplyTo":"17431.63509.670409.212654@cargo.ozlabs.ibm.com","subject":"Re: any problems with new branch of gitk?","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2006-03-15T13:00:28Z","receivedAt":"2006-03-15T13:00:28Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"On 3/15/06, Paul Mackerras <paulus@samba.org> wrote:\n>\n> > I don't if that was intended (see the screenshot attached), but some\n> > lines miss arrows. Click on where the arrow would be works (jump to\n> > counterpart arrow). Never have this with the old gitk.\n> >\n> > Tcl/Tk 8.4.9 (Gentoo).\n>\n> Yes, it seems that tk 8.4 can't draw arrows on the ends of diagonal\n> line segments.  The old gitk coped with this by simply shortening the\n> line until it got to a vertical line segment.  I can probably do\n> better than that with the new layout algorithm.  I'll look at it.\n>\n\nOk, thanks for confirmation. I wasn't sure if that's me, Gentoo, or tk.\n\nOn related note: do you know of any way to start gitk with sensible\nlayout under cygwin? I ended up with commenting out sourcing of\n.gitk. It produces a window compressed in one block, which I can\nresize and relayout later. Any other attempt to preset the size or\nlayout either can't be (literally) seen or can't be changed into something\nusable.\n"}]}