{"thread":{"id":"9318","subject":"git-gui i18n / 0.9.x plans","startedAt":"2007-07-31T01:28:04Z","lastAt":"2007-08-12T20:08:10Z","messageCount":5,"participants":["Shawn O. Pearce","Johannes Schindelin","Jean-François Veillette","Christian Stimming"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"49175","messageId":"20070731012804.GZ20052@spearce.org","threadId":"9318","inReplyTo":null,"subject":"git-gui i18n / 0.9.x plans","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-07-31T01:28:04Z","receivedAt":"2007-07-31T01:28:04Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Now that git-gui 0.8.0 has been released I have updated both the\nmaint and master branches to 0.8.0. maint will carry the 0.8.0\ndevelopment forward, and is strictly for bug fixes to the current\nnon-i18n codebase. I'm unlikely to make changes here except to\naddress current critical issues.\n\nRegarding future development for the off-in-the-future 0.9.0 release\nI'd like to see the i18n work merge in before we do anything else\nmajor to git-gui. I'm likely to shift my focus to fast-import this\nweek, which means git-gui will probably see no major activity from\nme for about the next two weeks. As soon as the i18n team has\nsomething rebased onto current master that is ready for merging,\nI'll bring it over. Yes, that's a promise on my part to try and\nkeep my tree frozen for a little while. :)\n\nOther things I'd like to do in 0.9.0, but may or may not actually\ndo myself:\n\n - Automatically refetch tracking branches in merge\n - Text mode log viewer:\n `git-log`, `git-log -g`\n - File monitor on WinNT (to avoid costly Rescan on large projects)\n - Remove more porcelain shell dependencies:\n `git-merge`, `git-repack`, `git-remote prune`\n - UI for cherry-pick/revert\n - Generational GC for 'Compress Database'\n - Integration with git-stash\n - Hunk splitting/selection\n - UI for git-tag\n - Push specific tags by name (rather than by --tags)\n - Pull from arbitrary URL/branch pair\n\nThose are roughly ordered by how much I think myself and my fellow\nday-job coworkers want these features, so that's probably roughly\nthe order I'll try to work through them after the i18n current\nchanges are merged in. Of course patches are also welcome. :)\n\nI haven't yet settled on whether the first i18n enabled version would\nbe 0.9.0 or a 0.8.1/2. That's one reason why I want to get the i18n\nchanges merged early. If we have a few high quality translations\nready to go I'd rather ship them in a 0.8.x maint release than hang\nonto them for another 1-2 months while the major features of the\n0.9.0 release get worked on and stablized.\n\n-- \nShawn.\n"},{"id":"49204","messageId":"Pine.LNX.4.64.0707311136540.14781@racer.site","threadId":"9318","inReplyTo":"20070731012804.GZ20052@spearce.org","subject":"Re: git-gui i18n / 0.9.x plans","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-07-31T10:47:30Z","receivedAt":"2007-07-31T10:47:30Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Mon, 30 Jul 2007, Shawn O. Pearce wrote:\n\n> Regarding future development for the off-in-the-future 0.9.0 release I'd \n> like to see the i18n work merge in before we do anything else major to \n> git-gui.\n\nVery good! As it happens, I pushed an update this morning. \ntemp-rebase-to-shawns-master is the branch which forward-ported all \npatches to the current master of git-gui.git.\n\nAs I understand, Christian will find and mark all strings lacking [mc ...] \nand update the .pot file. Then we'll kindly ask the good translators \n(thanks everyone!) to review the changes, and after that I'll prepare some \nsubmittable patch series (no need to have several patches per language).\n\n> - Hunk splitting/selection\n\nYeah, I am personally interested in this, so time permitting I will \ncontinue on that part. Regarding your idea from another post of yours: \nIMHO selections are only meaningful if they take whole lines. But that's \nalmost like hunk splitting, so it should be easy to support with the code \nI wrote and will have written.\n\nCiao,\nDscho\n"},{"id":"49221","messageId":"1E593130-7BBC-488D-88A5-2E16D68614A6@yahoo.ca","threadId":"9318","inReplyTo":"20070731012804.GZ20052@spearce.org","subject":"Re: git-gui i18n / 0.9.x plans","fromName":"Jean-François Veillette","fromEmail":"jean_francois_veillette@yahoo.ca","sentAt":"2007-07-31T13:38:23Z","receivedAt":"2007-07-31T13:38:23Z","isPatch":false,"sender":{"key":"jean_francois_veillette@yahoo.ca","avatar":null},"body":"\nLe 07-07-30 à 21:28, Shawn O. Pearce a écrit :\n> - UI for cherry-pick/revert\n> - Hunk splitting/selection\n\nIt would be nice to use the configured external merge tool (git \nmergetool) to help here (in my case os-x:opendiff/FileMerge).\nHaving a visual diff between\n- the repository and the index\n- the index and the workarea\n- the repository and the workarea\n\nSorry, I can't contribute (never touched tcl/tk), I can only \nsuggest ... and hope for the best.\n\n- jfv\n"},{"id":"49227","messageId":"20070731143228.GC20052@spearce.org","threadId":"9318","inReplyTo":"1E593130-7BBC-488D-88A5-2E16D68614A6@yahoo.ca","subject":"Re: git-gui i18n / 0.9.x plans","fromName":"Shawn O. Pearce","fromEmail":"spearce@spearce.org","sentAt":"2007-07-31T14:32:28Z","receivedAt":"2007-07-31T14:32:28Z","isPatch":false,"sender":{"key":"spearce@spearce.org","avatar":"https://avatars.githubusercontent.com/u/34844?v=4"},"body":"Jean-Fran??ois Veillette wrote:\n> Le 07-07-30 à 21:28, Shawn O. Pearce a écrit :\n> > - UI for cherry-pick/revert\n> > - Hunk splitting/selection\n> \n> It would be nice to use the configured external merge tool (git \n> mergetool) to help here (in my case os-x:opendiff/FileMerge).\n> Having a visual diff between\n> - the repository and the index\n> - the index and the workarea\n> - the repository and the workarea\n\nHmm. According to the manual[1]:\n\n opendiff file1 file2 [-ancestor ancestorFile] [-merge mergeFile]\n\nwhat should be the file1/file2/ancesorFile here?\n\nAnother problem is this paragraph:\n\n opendiff exits immediately after the comparison request has been\n sent to FileMerge.\n\nUhhhh... how does git-gui know the user is done and the mergeFile\nshould be staged?\n\nI'm also on OS X (its my primary development system for git-gui)\nso I might consider working on this, but after looking at the\nmanpage I'm not so sure...\n\n\n[1] http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/opendiff.1.html\n\n-- \nShawn.\n"},{"id":"50588","messageId":"200708122208.11307.stimming@tuhh.de","threadId":"9318","inReplyTo":"Pine.LNX.4.64.0707311136540.14781@racer.site","subject":"Re: git-gui i18n / 0.9.x plans","fromName":"Christian Stimming","fromEmail":"stimming@tuhh.de","sentAt":"2007-08-12T20:08:10Z","receivedAt":"2007-08-12T20:08:10Z","isPatch":false,"sender":{"key":"stimming@tuhh.de","avatar":"https://avatars.githubusercontent.com/u/227778?v=4"},"body":"Am Dienstag, 31. Juli 2007 12:47 schrieb Johannes Schindelin:\n> On Mon, 30 Jul 2007, Shawn O. Pearce wrote:\n> > Regarding future development for the off-in-the-future 0.9.0 release I'd\n> > like to see the i18n work merge in before we do anything else major to\n> > git-gui.\n\nThat sounds very good. Of course I'm very interested in having a i18n'ized \ngit-gui available as soon as possible. In the git-gui-i18n.git code I think \nwe've by now covered really all of the strings that appear throughout the \nprogram. Thanks to Johannes' maintenance work, the i18n patches are based on \nyour (almost) latest master. Once the translation will actually be accepted \ninto git-gui.git, I will also spend some weeks on final polish for the \nglossary and the German translation. I think it will be possible for you to \noffer at least a few language in complete translations in a 0.8.x release.\n\n> Very good! As it happens, I pushed an update this morning.\n> temp-rebase-to-shawns-master is the branch which forward-ported all\n> patches to the current master of git-gui.git.\n>\n> As I understand, Christian will find and mark all strings lacking [mc ...]\n> and update the .pot file. Then we'll kindly ask the good translators\n> (thanks everyone!) to review the changes, and after that I'll prepare some\n> submittable patch series (no need to have several patches per language).\n\nYes, this is how this should work. I'm looking forward to a fully i18n'ized \ngit-gui! Thanks for this great program.\n\nChristian\n"}]}