{"thread":{"id":"1444","subject":"Re: qgit-0.81","startedAt":"2005-08-07T07:37:09Z","lastAt":"2005-08-07T07:37:09Z","messageCount":1,"participants":["Marco Costalba"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"6900","messageId":"20050807073709.8962.qmail@web26302.mail.ukl.yahoo.com","threadId":"1444","inReplyTo":null,"subject":"Re: qgit-0.81","fromName":"Marco Costalba","fromEmail":"mcostalba@yahoo.it","sentAt":"2005-08-07T07:37:09Z","receivedAt":"2005-08-07T07:37:09Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":"Linus Torvalds wrote:\n\n>Ok, this is nicer than gitk, with the parents showing up in the commit\n>message and thus easy to go to. You might add children too: it's not\n>something git itself knows about intrisically, but since you've already \n>built the graph, at least you see what children are part of that graph..\n>\n\nI don't know if this is what you mean, but if you right click on a free \nlane (i.e. not a bullet but a vertical line) on the graph you should see a\npop-up with selectable childs and parent.\n\n> - Any chance of having a git archive of qgit? I realize that sourceforge \n>   doesn't have git archives, but (a) maybe you can ask and (b) maybe \n>   there are alternate places you could put it. It's just sad having to \n>   download tar-balls.\n>\n\nI will try to proceed from (a) to, eventually, (b).\n\n\n> - The qgit graph is not as pretty as the gitk one. Any chance of making \n>   the bullets a bit smaller, and having an option to not do the\n>   \"jump-over-bumps\"?\n>\n\nOk, I will try to use straight horizontal lines instead of jump-over-bumps. If\nthis seems not enough clear I will add an option to switch visualization.\n\n> - the \"file annotation\" window is nice, but it _really_ shouldn't do line\n>   wrapping. If you make the window narrower, you'll see it wrap and look \n>   horrible.. Are all text windows always wrapped in QT?\n>\n\nNo, just a setting. Not a problem to set \"No wrap\" behaviour. I will set this\nalso in diff viewer window.\n\n> - You edit the commit comments heavily, and have no options to unedit. \n>   For example, I need the emails in the sign-offs if I ever cut-and-paste \n>   to an email client when I sent a \"hey, this commit broke so-and-so..\"\n>\n\nYou discover a real bug ;-). I never intended to modify commit comments in any way.\n\n\n> - the \"format a patch to be sent as email\" thing says \"at least two \n>   revisions needed\" when you only have one. Why? One of my more common \n>   cases is that I send one commit as a patch, and now I do\n>\n>\tgit-diff-tree -p --pretty [commit-id] > ~/diff\n>\n>   and then just send that. A single commit _does_ describe a valid patch, \n>   after all.\n>\n\nThe logic here is to specify a range. As example if you have following commits\n\n      A\n      B\n      C\n      D\n      E\n      F\n\nand you select B and E then 3 patches will be created: \n \n     patch_1(diff between D-E)\n     patch_2(diff between C-D)\n     patch_3(diff between B-C) \n\nSo you need at least 2 selected revs. Put in other words, the base is always explicit.\n\n \nMarco\n\n\n__________________________________________________\nDo You Yahoo!?\nTired of spam?  Yahoo! Mail has the best spam protection around \nhttp://mail.yahoo.com \n"}]}