{"thread":{"id":"6287","subject":"Getting gitk to display all refs but stgit logs","startedAt":"2007-01-08T21:32:59Z","lastAt":"2007-01-09T21:31:41Z","messageCount":4,"participants":["Yann Dirson","Marco Costalba"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"31163","messageId":"20070108213259.GB17093@nan92-1-81-57-214-146.fbx.proxad.net","threadId":"6287","inReplyTo":null,"subject":"Getting gitk to display all refs but stgit logs","fromName":"Yann Dirson","fromEmail":"ydirson@altern.org","sentAt":"2007-01-08T21:32:59Z","receivedAt":"2007-01-08T21:32:59Z","isPatch":false,"sender":{"key":"ydirson@altern.org","avatar":"https://avatars.githubusercontent.com/u/1190950?v=4"},"body":"Since v0.11, StGIT creates references to keep a hand on patch logs.\nThis has the unfortunate side-effect that \"gitk --all\" suddenly shows\nall those very annoying, and soon becomes unusable on\nrepositories for which was very convenient.\n\nI guess it would be acceptable to have stgit itself launch gitk with\nthe correct options.\n\nThe only way I could find to suppress these refs from the display is\nto find the refs ourselves and pipe them to gitk using --stdin:\n\n find .git/refs/ -type f -not -name '*.log' -printf '%P\\n'|gitk --stdin\n\nUnfortunately, requesting an update from gitk then behaves as if\nnothing had been given on command-line (obviously it is passing\n--stdin to git-rev-list without repeating the data).\n\nWe could do slightly better by enclosing the find in backquotes on the\ngitk command-line, but that would still hide new refs to git-rev-list\nwhen updating the graph.\n\nIs there a better way already, or should we work on something specific\nhere ? A possible solution I think of could be to call something like:\n\n gitk --stdin-command=\"find .git/refs/ -type f -not -name '*.log' -printf '%P\\n'\"\n\nBest regards,\n-- \nYann.\n"},{"id":"31237","messageId":"e5bfff550701090417g3f8ab697n709721939ab36f5d@mail.gmail.com","threadId":"6287","inReplyTo":"20070108213259.GB17093@nan92-1-81-57-214-146.fbx.proxad.net","subject":"Re: Getting gitk to display all refs but stgit logs","fromName":"Marco Costalba","fromEmail":"mcostalba@gmail.com","sentAt":"2007-01-09T12:17:57Z","receivedAt":"2007-01-09T12:17:57Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":"On 1/8/07, Yann Dirson wrote:\n> Since v0.11, StGIT creates references to keep a hand on patch logs.\n> This has the unfortunate side-effect that \"gitk --all\" suddenly shows\n> all those very annoying, and soon becomes unusable on\n> repositories for which was very convenient.\n>\n\nNormally you only need branch names\n\ngitk/qgit --all --> practically equivalent to --> gitk/qgit \n\nThis is already done internally in qgit when, as example, retrieving a\nfile history to annotate.\n"},{"id":"31271","messageId":"20070109194108.GC17093@nan92-1-81-57-214-146.fbx.proxad.net","threadId":"6287","inReplyTo":"e5bfff550701090417g3f8ab697n709721939ab36f5d@mail.gmail.com","subject":"Re: Getting gitk to display all refs but stgit logs","fromName":"Yann Dirson","fromEmail":"ydirson@altern.org","sentAt":"2007-01-09T19:41:08Z","receivedAt":"2007-01-09T19:41:08Z","isPatch":false,"sender":{"key":"ydirson@altern.org","avatar":"https://avatars.githubusercontent.com/u/1190950?v=4"},"body":"On Tue, Jan 09, 2007 at 01:17:57PM +0100, Marco Costalba wrote:\n> On 1/8/07, Yann Dirson wrote:\n> >Since v0.11, StGIT creates references to keep a hand on patch logs.\n> >This has the unfortunate side-effect that \"gitk --all\" suddenly shows\n> >all those very annoying, and soon becomes unusable on\n> >repositories for which was very convenient.\n> >\n> \n> Normally you only need branch names\n> \n> gitk/qgit --all --> practically equivalent to --> gitk/qgit branch names>\n\nNot exactly. While qgit has knowledge of StGIT stacks and displays\nunapplied patches [1], gitk does not, and requesting a branch only\nshows the applied patches. I have no opinion whether gitk should be\ntaught about them, but I'd like it to be usable on them anyway.\n\nOne thing that qgit also does not show, but which I regularly use when\nviewing StGIT stacks in gitk, is the ancestry of unapplied patches\n(eg. you can see at first glance whether an unapplied patch is\nuptodate, or has not been ported yet atop the currently-applied ones.\n\n[1] BTW, as of 1.5.3 it displays them backwards, causing all sors of\nproblems - I've not yet collected all of my comments for you, but at\nleast that one is sent now ;)\n\nBest regards,\n-- \nYann.\n"},{"id":"31287","messageId":"e5bfff550701091331u300e9947r922a632327b8c37f@mail.gmail.com","threadId":"6287","inReplyTo":"20070109194108.GC17093@nan92-1-81-57-214-146.fbx.proxad.net","subject":"Re: Getting gitk to display all refs but stgit logs","fromName":"Marco Costalba","fromEmail":"mcostalba@gmail.com","sentAt":"2007-01-09T21:31:41Z","receivedAt":"2007-01-09T21:31:41Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":"On 1/9/07, Yann Dirson wrote:\n>\n> [1] BTW, as of 1.5.3 it displays them backwards, causing all sors of\n> problems - I've not yet collected all of my comments for you, but at\n> least that one is sent now ;)\n\nI have quick tested on my StGit repo and all qgit versions back to\nqgit-1.2 show the same unapplied patches in the same sequence. Perhaps\nsomething has changed in StGit or in git-rev-list in the meantime.\n\nBTW qgit uses the following command to get the unapplied patches:\n\ngit rev-list --header --parents ^HEAD\n\nWhere info is retrieved from StGit (well, with\nsome shortcuts ;-) to speed up the thing).\n\nP.S: The above 'git rev-list' command returns _also_ spurious revs\nthat must be filtered out matching against the given \n"}]}