{"thread":{"id":"6318","subject":"[ANNOUNCE] qgit4 aka qgit ported to Windows","startedAt":"2007-01-09T21:14:00Z","lastAt":"2007-01-11T13:24:39Z","messageCount":13,"participants":["Marco Costalba","Josef Weidendorfer","Yann Dirson","Martin Langhoff","Johannes Schindelin","Johannes Sixt","Andreas Ericsson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"31283","messageId":"e5bfff550701091314k71e282e8x125db65d5c287a94@mail.gmail.com","threadId":"6318","inReplyTo":null,"subject":"[ANNOUNCE] qgit4 aka qgit ported to Windows","fromName":"Marco Costalba","fromEmail":"mcostalba@gmail.com","sentAt":"2007-01-09T21:14:00Z","receivedAt":"2007-01-09T21:14:00Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":"I have setup, (thanks Pasky) the repository\n\n     git://repo.or.cz/qgit4.git\n\n\nWith an experimental version of qgit, called qgit4.\n\nFeatures are the same of qgit-1.5.4  release but has been ported under\nQt4.2 libraries from Qt3, this means that could be compiled and run as\na Windows native application.\n\nQt4.2 is available as GPL for non commercial purposes also for Windows platform.\n\nSo what you need is:\n\n1) Qt4.2 already packaged with MinGW for windows\n(http://www.trolltech.com/developer/downloads/qt/windows)\n\n2) Cygwin with git files\n\n3) qgit sources from the above public repository\n\n4) Compile using qmake that will build proper Makefile for you\n\n    - qmake qgit.pro\n    - make\n    - (make install is supported only under Linux at the moment)\n\n5) Open a terminal with cmd.exe, add Qt and MinGW bin dirs to PATH\n(already added if you run the ready to use Qt command prompt menu that\ncomes with Qt installation), add cygwin bin directory to PATH,\nsomething like:\n\n               set PATH=%PATH%;C:\\cygwin\\bin\\directory\n\n\n6) Start qgit.exe\n\n7) Have fun\n\nNOTE NOTE: DO NOT RUN from a cygwin terminal, as I said qgit it's a\n*native* Windows application when compiled with Qt4.2 so you don't\nneed that.\n\nWell, I have tried to run from a cygwin terminal and it works almost\nthe same (of course you need to add Qt and MinGW bin dirs to path as\nalways) but it's much slower and has some little issues with the\ndifferent paths conventions.\n\nNOTE: This is 'alpha' quality software, not all features are already\nworking so be prepared to few surprises.\n\nMarco\n\nP.S: Of course the same sources work (better) also under Linux.\n"},{"id":"31294","messageId":"200701092255.17091.Josef.Weidendorfer@gmx.de","threadId":"6318","inReplyTo":"e5bfff550701091314k71e282e8x125db65d5c287a94@mail.gmail.com","subject":"Re: [ANNOUNCE] qgit4 aka qgit ported to Windows","fromName":"Josef Weidendorfer","fromEmail":"josef.weidendorfer@gmx.de","sentAt":"2007-01-09T21:55:16Z","receivedAt":"2007-01-09T21:55:16Z","isPatch":false,"sender":{"key":"josef.weidendorfer@gmx.de","avatar":null},"body":"On Tuesday 09 January 2007 22:14, Marco Costalba wrote:\n> I have setup, (thanks Pasky) the repository\n> \n>      git://repo.or.cz/qgit4.git\n> \n> \n> With an experimental version of qgit, called qgit4.\n\nNice.\n\nWhy not as branch in the original qgit repository?\nYou are losing all your history this way.\n\nJosef\n"},{"id":"31297","messageId":"e5bfff550701091430r759c083bse99bd79046f3205f@mail.gmail.com","threadId":"6318","inReplyTo":"200701092255.17091.Josef.Weidendorfer@gmx.de","subject":"Re: [ANNOUNCE] qgit4 aka qgit ported to Windows","fromName":"Marco Costalba","fromEmail":"mcostalba@gmail.com","sentAt":"2007-01-09T22:30:34Z","receivedAt":"2007-01-09T22:30:34Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":"On 1/9/07, Josef Weidendorfer <Josef.Weidendorfer@gmx.de> wrote:\n> On Tuesday 09 January 2007 22:14, Marco Costalba wrote:\n> > I have setup, (thanks Pasky) the repository\n> >\n> >      git://repo.or.cz/qgit4.git\n> >\n> >\n> > With an experimental version of qgit, called qgit4.\n>\n> Nice.\n>\n> Why not as branch in the original qgit repository?\n> You are losing all your history this way.\n>\n\nWell, Qt4 it's completely different from Qt3, porting it's a nice way\nto say rewrite. So moving patches between the two branches it's very\ndifficult already now and it will be impossible in a near future not\nbecause of development forking, but because of API. This means two\ndifferent and *not mergeable* branches.\n\nBeing not mergeable they lose the main motivation to be in the same\nrepository IMHO. Also I would like to continue to support and improve\nthe stable and proven Qt3 version on kernel.org that is and will be\nthe main version.\n\nPerhaps when qgit4 will be stable enough I will ask to move to\nkernel.org but now, for easier development I asked to Pasky, that\nkindly accepted, to host this repo.\n\nMarco\n"},{"id":"31300","messageId":"20070109224723.GG17093@nan92-1-81-57-214-146.fbx.proxad.net","threadId":"6318","inReplyTo":"e5bfff550701091430r759c083bse99bd79046f3205f@mail.gmail.com","subject":"Re: [ANNOUNCE] qgit4 aka qgit ported to Windows","fromName":"Yann Dirson","fromEmail":"ydirson@altern.org","sentAt":"2007-01-09T22:47:23Z","receivedAt":"2007-01-09T22:47:23Z","isPatch":false,"sender":{"key":"ydirson@altern.org","avatar":"https://avatars.githubusercontent.com/u/1190950?v=4"},"body":"On Tue, Jan 09, 2007 at 11:30:34PM +0100, Marco Costalba wrote:\n> Being not mergeable they lose the main motivation to be in the same\n> repository IMHO.\n\nWell, this also means you lose the history trail of you project.  Just\nsuppose one day you'll face a piece of your code which you don't\nunderstand any more (face it, we all have that strange \"did *I* write\nthat ?\" feeling some day ;).  Being able to hunt it down is nice - and\ngrafting the qt3-based repo will only be useful it you know precisely\nwhere to put the graft...\n\nBest regards,\n-- \nYann.\n"},{"id":"31419","messageId":"46a038f90701101517s1d5e818eq2fba220d17a6aa03@mail.gmail.com","threadId":"6318","inReplyTo":"e5bfff550701091314k71e282e8x125db65d5c287a94@mail.gmail.com","subject":"Re: [ANNOUNCE] qgit4 aka qgit ported to Windows","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2007-01-10T23:17:43Z","receivedAt":"2007-01-10T23:17:43Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On 1/10/07, Marco Costalba <mcostalba@gmail.com> wrote:\n> 6) Start qgit.exe\n> 7) Have fun\n\nGreat!\n\nHow much does qgit4 depend on using commandline git? IOWs, how far\nfrom not needing cygwin+git, and shipping a git+qgit compiled against\nthe MinGW that QT4 has?\n\ncheers,\n\n\nmartin\n"},{"id":"31440","messageId":"Pine.LNX.4.63.0701110944420.22628@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"6318","inReplyTo":"46a038f90701101517s1d5e818eq2fba220d17a6aa03@mail.gmail.com","subject":"Re: [ANNOUNCE] qgit4 aka qgit ported to Windows","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-01-11T08:47:40Z","receivedAt":"2007-01-11T08:47:40Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 11 Jan 2007, Martin Langhoff wrote:\n\n> On 1/10/07, Marco Costalba <mcostalba@gmail.com> wrote:\n> > 6) Start qgit.exe\n> > 7) Have fun\n> \n> Great!\n> \n> How much does qgit4 depend on using commandline git? IOWs, how far\n> > from not needing cygwin+git, and shipping a git+qgit compiled against\n> the MinGW that QT4 has?\n\nI do not understand what QT4 has to do with git compiling against MinGW. \nIt is a totally different kind of kettle.\n\nI outlined the difficulties with MinGW already, see \ne.g.http://article.gmane.org/gmane.comp.version-control.git/14047\n\nCiao,\nDscho\n"},{"id":"31445","messageId":"45A604ED.5EF73A1E@eudaptics.com","threadId":"6318","inReplyTo":"46a038f90701101517s1d5e818eq2fba220d17a6aa03@mail.gmail.com","subject":"MinGW port (was: Re: [ANNOUNCE] qgit4 aka qgit ported to Windows)","fromName":"Johannes Sixt","fromEmail":"j.sixt@eudaptics.com","sentAt":"2007-01-11T09:35:41Z","receivedAt":"2007-01-11T09:35:41Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Martin Langhoff wrote:\n> How much does qgit4 depend on using commandline git? IOWs, how far\n> from not needing cygwin+git, and shipping a git+qgit compiled against\n> the MinGW that QT4 has?\n\nFWIW, I'm slowly working on a MinGW port of git, based on Dscho's\ninitial work.\n\nCurrently, the tool set passes about 60-70% of the tests.\n\nThis works: The tools that you commonly need to work on a local repo,\nexcept merges ([*]): commit, rebase, reset, log, diff and their\nplumbing.\n\nThis does not work: pull, fetch, clone; mostly due to fork()\ndifficulties in their plumbing (fetch-pack, send-pack, etc.)\n\n[*] because shell scripts like merge-one-file can't be invoked from an\nexe like merge-index, yet. Fortunately this looks like the easiest part\nto solve.\n\n-- Hannes\n"},{"id":"31447","messageId":"Pine.LNX.4.63.0701111037330.22628@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"6318","inReplyTo":"45A604ED.5EF73A1E@eudaptics.com","subject":"Re: MinGW port (was: Re: [ANNOUNCE] qgit4 aka qgit ported to Windows)","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-01-11T09:39:23Z","receivedAt":"2007-01-11T09:39:23Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 11 Jan 2007, Johannes Sixt wrote:\n\n> This works: The tools that you commonly need to work on a local repo,\n> except merges ([*]): commit, rebase, reset, log, diff and their\n> plumbing.\n> \n> [...]\n> \n> [*] because shell scripts like merge-one-file can't be invoked from an \n> exe like merge-index, yet. Fortunately this looks like the easiest part \n> to solve.\n\nExactly. Just build-in merge-one-file. This has the further benefit that \nwe (finally) can use the inbuilt xdl_merge() without a fork()!\n\nAnd then, we'll get Alex' merge under 1 minute.\n\nCiao,\nDscho\n"},{"id":"31466","messageId":"e5bfff550701110419v3508e9d5gbc206b7d0fa320ae@mail.gmail.com","threadId":"6318","inReplyTo":"46a038f90701101517s1d5e818eq2fba220d17a6aa03@mail.gmail.com","subject":"Re: [ANNOUNCE] qgit4 aka qgit ported to Windows","fromName":"Marco Costalba","fromEmail":"mcostalba@gmail.com","sentAt":"2007-01-11T12:19:56Z","receivedAt":"2007-01-11T12:19:56Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":"On 1/11/07, Martin Langhoff <martin.langhoff@gmail.com> wrote:\n> On 1/10/07, Marco Costalba <mcostalba@gmail.com> wrote:\n> > 6) Start qgit.exe\n> > 7) Have fun\n>\n> Great!\n>\n> How much does qgit4 depend on using commandline git? IOWs, how far\n> from not needing cygwin+git, and shipping a git+qgit compiled against\n> the MinGW that QT4 has?\n>\n\nqgit4 does not depends on  commandline git environment at all. You can\nstart qgit4 also without a git installation, also without a cygwin\ninstallation either. Of course it's not useful in that cases.\n\nI had no time to fix some rogh edges regarding launching qgit4 with\nproper paths set. What I plan to do this week end is to find an 'easy\nto use recipe' to start qgit4 from cmd.exe, from desktop icon and also\nfrom cygwin shell.\n\nI need to experiment a little bit with this but I would like to add\ninternal automatic recognizing of environment at least for cmd.exe vs\ncygwin shell launching case so to let user have a nice experience in\nboth cases.\n\n  Marco\n"},{"id":"31467","messageId":"45A62D40.5040707@op5.se","threadId":"6318","inReplyTo":"e5bfff550701110419v3508e9d5gbc206b7d0fa320ae@mail.gmail.com","subject":"Re: [ANNOUNCE] qgit4 aka qgit ported to Windows","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2007-01-11T12:27:44Z","receivedAt":"2007-01-11T12:27:44Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"Marco Costalba wrote:\n> On 1/11/07, Martin Langhoff <martin.langhoff@gmail.com> wrote:\n>> On 1/10/07, Marco Costalba <mcostalba@gmail.com> wrote:\n>> > 6) Start qgit.exe\n>> > 7) Have fun\n>>\n>> Great!\n>>\n>> How much does qgit4 depend on using commandline git? IOWs, how far\n>> from not needing cygwin+git, and shipping a git+qgit compiled against\n>> the MinGW that QT4 has?\n>>\n> \n> qgit4 does not depends on  commandline git environment at all. You can\n> start qgit4 also without a git installation, also without a cygwin\n> installation either. Of course it's not useful in that cases.\n> \n\nHuh? Does qgit4 have all the git plumbing built in?\n\n-- \nAndreas Ericsson                   andreas.ericsson@op5.se\nOP5 AB                             www.op5.se\nTel: +46 8-230225                  Fax: +46 8-230231\n"},{"id":"31468","messageId":"e5bfff550701110449j4feceb4fi42809bbbecde9ad6@mail.gmail.com","threadId":"6318","inReplyTo":"45A62D40.5040707@op5.se","subject":"Re: [ANNOUNCE] qgit4 aka qgit ported to Windows","fromName":"Marco Costalba","fromEmail":"mcostalba@gmail.com","sentAt":"2007-01-11T12:49:23Z","receivedAt":"2007-01-11T12:49:23Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":"On 1/11/07, Andreas Ericsson <ae@op5.se> wrote:\n> Marco Costalba wrote:\n> > On 1/11/07, Martin Langhoff <martin.langhoff@gmail.com> wrote:\n> >> On 1/10/07, Marco Costalba <mcostalba@gmail.com> wrote:\n> >> > 6) Start qgit.exe\n> >> > 7) Have fun\n> >>\n> >> Great!\n> >>\n> >> How much does qgit4 depend on using commandline git? IOWs, how far\n> >> from not needing cygwin+git, and shipping a git+qgit compiled against\n> >> the MinGW that QT4 has?\n> >>\n> >\n> > qgit4 does not depends on  commandline git environment at all. You can\n> > start qgit4 also without a git installation, also without a cygwin\n> > installation either. Of course it's not useful in that cases.\n> >\n>\n> Huh? Does qgit4 have all the git plumbing built in?\n>\n\nNo. It's absolutely not useful without git (but compiles and runs\nanyway). What I mean is that beign a native windows application it\ndoes not need cygwin. The latter is needed only by git.\n"},{"id":"31469","messageId":"e5bfff550701110456y51b8b678s59974cc1d8655a90@mail.gmail.com","threadId":"6318","inReplyTo":"Pine.LNX.4.63.0701111037330.22628@wbgn013.biozentrum.uni-wuerzburg.de","subject":"Re: MinGW port (was: Re: [ANNOUNCE] qgit4 aka qgit ported to Windows)","fromName":"Marco Costalba","fromEmail":"mcostalba@gmail.com","sentAt":"2007-01-11T12:56:09Z","receivedAt":"2007-01-11T12:56:09Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":"On 1/11/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:\n> Hi,\n>\n> On Thu, 11 Jan 2007, Johannes Sixt wrote:\n>\n> > This works: The tools that you commonly need to work on a local repo,\n> > except merges ([*]): commit, rebase, reset, log, diff and their\n> > plumbing.\n> >\n> > [...]\n> >\n> > [*] because shell scripts like merge-one-file can't be invoked from an\n> > exe like merge-index, yet. Fortunately this looks like the easiest part\n> > to solve.\n>\n\n>From an exe you could run:\n\n     cmd.exe /c  <script with arguments>\n\nOf course the problem is that the content of the script should be\nunderstandable by cmd.exe windows interpreter.\n"},{"id":"31473","messageId":"45A63A97.E160751F@eudaptics.com","threadId":"6318","inReplyTo":"e5bfff550701110456y51b8b678s59974cc1d8655a90@mail.gmail.com","subject":"Re: MinGW port (was: Re: [ANNOUNCE] qgit4 aka qgit ported to Windows)","fromName":"Johannes Sixt","fromEmail":"j.sixt@eudaptics.com","sentAt":"2007-01-11T13:24:39Z","receivedAt":"2007-01-11T13:24:39Z","isPatch":false,"sender":{"key":"j6t@kdbg.org","avatar":"https://avatars.githubusercontent.com/u/14810926?v=4"},"body":"Marco Costalba wrote:\n> > On Thu, 11 Jan 2007, Johannes Sixt wrote:\n> > > [*] because shell scripts like merge-one-file can't be invoked from an\n> > > exe like merge-index, yet. Fortunately this looks like the easiest part\n> > > to solve.\n> >\n> \n> >From an exe you could run:\n> \n>      cmd.exe /c  <script with arguments>\n> \n> Of course the problem is that the content of the script should be\n> understandable by cmd.exe windows interpreter.\n\nWe are talking about git's own scripts, which are (ba)sh and perl.\n\nThe route I'm going is to do the path lookup manually (if necessary),\nthen look at the first few bytes of the file for the interpreter, then\nsomething like\n\n spawnvp(<interpreter-w/o-path>, <full-path-of-script plus args>)\n\n-- Hannes\n"}]}