{"thread":{"id":"13178","subject":"Unresolved issues","startedAt":"2008-04-19T08:19:22Z","lastAt":"2008-04-21T17:59:28Z","messageCount":4,"participants":["Junio C Hamano","Teemu Likonen","Adam Simpkins","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"74745","messageId":"7vbq46fe9h.fsf@gitster.siamese.dyndns.org","threadId":"13178","inReplyTo":null,"subject":"Unresolved issues","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2008-04-19T08:19:22Z","receivedAt":"2008-04-19T08:19:22Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Here is an \"issues\" list I am keeping track of on the back of my head (and\nin \"TODO\" file on 'todo' branch, which is not updated often enough).\n\nThe tail end of this list is probably a bit stale, as I am running out of\ntime tonight and did not have enough time to check the current status.\nPlease spot issues that have been resolved and report them.\n\n----------------------------------------------------------------\n\nPossible bug not diagnosed yet\n\n* \"git commit --interactive\" allows same tree as parent to be recorded\n\nMessage-ID: <slrng059n3.nd8.joerg@alea.gnuu.de>\n\n----------------------------------------------------------------\n\nIssues that are unconcluded or need a fresh infusion of kerosene to\nfirestart them again.\n\n* adding across symlinks (me)\n\nMessage-ID: <7vd4oppllw.fsf@gitster.siamese.dyndns.org>\n\n* cvsserver improvements (Fredrik Noring)\n\nNeeds third-party confirmation and then properly applicable patches.\n\n* reworking rebase interactive (Jörg Sommer)\n\nMessage-Id: <1208132469-26471-1-git-send-email-joerg@alea.gnuu.de>\nMessage-Id: <1208169584-15931-1-git-send-email-joerg@alea.gnuu.de>\n\n* log --graph (Adam Simpkins)\n\nMessage-ID: <20080406214445.GA5822@adamsimpkins.net>\n\n* --pretty=format:%d (Dscho)\n\n* SP in path to $GIT_DIR breaks some scripts and many tests (Bryan Donlan)\n\nMessage-ID: <20080410084820.GA1904@shion.is.fushizen.net>\n\n* Prepare cvsimport for fixed cvsps (David Mansfield)\n\nMessage-Id: <1207100091.10532.64.camel@gandalf.cobite.com>\n\n* ff=only (Sverre Hvammen Johansen)\n  $gmane/78250\n\n* more help backends (Christian Couder)\n  $gmane/78150\n\n* cvsserver updates (Damien Diederen with help by Frank Lichtenheld)\n  $gmane/78188\n\n* rewriting annotated tags in filter-branch (Brandon Casey)\n  $gmane/78286\n\n* fsck --lost-found (me)\n  $gmane/78267\n\n* core.inithook (Dscho)\n  $gmane/78123\n\n* receive.localBranches = { refuse | allow } (Dscho)\n  $gmane/78065\n\n* autosetting core.ignorecase (Dmitry Potapov)\n  $gmane/78176\n\n* mailinfo extention to extract Message-ID and others (Anton Gladkov)\n  $gmane/78006\n\n* rebase -p\n  $gmane/78074\n\n  There is a quite well done series from Jörg Sommer I have to queue but\n  I am getting the feeling that it did not get enough review from the\n  list.  I am reading it through (slowly) myself, but I'd appreciate more\n  review comments on the list (not limited to this series).\n\n* synopsys: use {} instead of () for grouping alternatives (Jari Aalto)\n  $gmane/72243\n\n* \"[alias] st = status\" and \"cd .git && git st\" (Jeff King)\n  $gmane/72327\n\n* \"git fetch\" does not exit with non-zero status when it failed to update\n  some refs due to non-ffness (Daniel)\n  $gmane/77178\n\n* use \"assume unchanged\" bit to implement narrow checkout\n  $gmane/77046\n\n* zlib abstraction (Marco)\n  $gmane/72262\n\n* git --index-file=<foo> <cmd> (Linus)\n  $gmane/77332\n\n* git lost-found vs git fsck --lost-found\n  $gmane/78267\n"},{"id":"74806","messageId":"20080420154848.GA8647@mithlond.arda.local","threadId":"13178","inReplyTo":"7vbq46fe9h.fsf@gitster.siamese.dyndns.org","subject":"Re: Unresolved issues, \"log --graph\"","fromName":"Teemu Likonen","fromEmail":"tlikonen@iki.fi","sentAt":"2008-04-20T15:48:48Z","receivedAt":"2008-04-20T15:48:48Z","isPatch":false,"sender":{"key":"tlikonen@iki.fi","avatar":null},"body":"Junio C Hamano wrote (2008-04-19 01:19 -0700):\n\n> Here is an \"issues\" list I am keeping track of on the back of my head\n> (and in \"TODO\" file on 'todo' branch, which is not updated often\n> enough).\n\n> * log --graph (Adam Simpkins)\n\nHi Adam, any changes for modifying the \"log --graph\" patch series to\nmake it apply to the current development version of git? It would just\nfeel wrong if this apparently well-designed tool was left behind. Of\ncourse it's up to you.\n\nSome thoughts on the graph functionality: I have understood that many\nBazaar people like the way \"bzr log\" indents the log entries which\noriginate from other branches. This way Bazaar users can easily think in\nterms of commits in the mainline and commits originating from feature\nbranches. I think this is useful distinction sometimes.\n\nI just realised that Adam's \"git log --graph\" offers the same\nfunctionality as \"bzr log\" but much better. With \"git log --graph\" user\ncan see the history the way \"bzr log\" displays it: the current branch is\non the leftmost graph line and can be seen as the \"mainline\" (if\nwanted); commits coming from other branches are indented and appear in\nseparate graph lines. Yes, there is, and have been, \"gitk\" of course.\n\"log --graph\" is just much closer to \"bzr log\" view. I think \"git log\"\nis quite superiour as it allows many ways of viewing history.\n"},{"id":"74875","messageId":"20080421173312.GA18367@adamsimpkins.net","threadId":"13178","inReplyTo":"20080420154848.GA8647@mithlond.arda.local","subject":"Re: Unresolved issues, \"log --graph\"","fromName":"Adam Simpkins","fromEmail":"adam@adamsimpkins.net","sentAt":"2008-04-21T17:33:12Z","receivedAt":"2008-04-21T17:33:12Z","isPatch":false,"sender":{"key":"adam@adamsimpkins.net","avatar":"https://gravatar.com/avatar/d3fd2c0b3e2d2136b56e95726ee03227bee4eb562f627dcd3ebca0623fa05054?d=mp&s=160"},"body":"On Sun, Apr 20, 2008 at 06:48:48PM +0300, Teemu Likonen wrote:\n> Junio C Hamano wrote (2008-04-19 01:19 -0700):\n> \n> > Here is an \"issues\" list I am keeping track of on the back of my head\n> > (and in \"TODO\" file on 'todo' branch, which is not updated often\n> > enough).\n> \n> > * log --graph (Adam Simpkins)\n> \n> Hi Adam, any changes for modifying the \"log --graph\" patch series to\n> make it apply to the current development version of git? It would just\n> feel wrong if this apparently well-designed tool was left behind. Of\n> course it's up to you.\n\nYes.  I didn't mean to drop this, I've just haven't had much time to\nwork on it lately.  I may get a chance to work on it tomorrow,\notherwise I'll do it this coming weekend.\n\nI'll submit a new series of patches to apply the \"log --graph\" changes\nonto master.  I think the only thing that needs to be changed is to\nupdate my code to work with Junio's jc/terminator-separator changes.\nIt looks like it should be fairly straightforward.\n\nJunio and others, is there anything else I should do to make the \"log\n--graph\" changes ready for pu/next/master?\n\n-- \nAdam Simpkins\nadam@adamsimpkins.net\n"},{"id":"74877","messageId":"alpine.DEB.1.00.0804211859100.2298@eeepc-johanness","threadId":"13178","inReplyTo":"20080421173312.GA18367@adamsimpkins.net","subject":"Re: Unresolved issues, \"log --graph\"","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-04-21T17:59:28Z","receivedAt":"2008-04-21T17:59:28Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Mon, 21 Apr 2008, Adam Simpkins wrote:\n\n> On Sun, Apr 20, 2008 at 06:48:48PM +0300, Teemu Likonen wrote:\n> > Junio C Hamano wrote (2008-04-19 01:19 -0700):\n> > \n> > > Here is an \"issues\" list I am keeping track of on the back of my head\n> > > (and in \"TODO\" file on 'todo' branch, which is not updated often\n> > > enough).\n> > \n> > > * log --graph (Adam Simpkins)\n> > \n> > Hi Adam, any changes for modifying the \"log --graph\" patch series to\n> > make it apply to the current development version of git? It would just\n> > feel wrong if this apparently well-designed tool was left behind. Of\n> > course it's up to you.\n> \n> Yes.  I didn't mean to drop this, I've just haven't had much time to\n> work on it lately.  I may get a chance to work on it tomorrow,\n> otherwise I'll do it this coming weekend.\n> \n> I'll submit a new series of patches to apply the \"log --graph\" changes\n> onto master.  I think the only thing that needs to be changed is to\n> update my code to work with Junio's jc/terminator-separator changes.\n> It looks like it should be fairly straightforward.\n> \n> Junio and others, is there anything else I should do to make the \"log\n> --graph\" changes ready for pu/next/master?\n\nI look forward to it!\n\nCiao,\nDscho\n"}]}