{"thread":{"id":"21768","subject":"qgit question: tagged commits not on a branch","startedAt":"2009-11-26T21:54:44Z","lastAt":"2009-11-27T17:21:33Z","messageCount":3,"participants":["Chris.Cheney","Michael J Gruber"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"128508","messageId":"Xns9CCFDEF02D061ChrisCheneytesconet@80.91.229.13","threadId":"21768","inReplyTo":null,"subject":"qgit question: tagged commits not on a branch","fromName":"Chris.Cheney","fromEmail":"chris.cheney.nospam@tesco.net","sentAt":"2009-11-26T21:54:44Z","receivedAt":"2009-11-26T21:54:44Z","isPatch":false,"sender":{"key":"chris.cheney.nospam@tesco.net","avatar":null},"body":"My commit graph has a number of forks (I can't use the word \"branches\" \nhere) that are referenced only by a tag. Whereas gitk --all displays this \ngraph including those forks, qgit does not display those forks - I don't \nsee a way to make it do so, other than by adding branches to those tagged \ncommits. \n\nHave I overlooked something?\n\nTIA\n\nChris\n"},{"id":"128568","messageId":"4B0FECFA.9040307@drmicha.warpmail.net","threadId":"21768","inReplyTo":"Xns9CCFDEF02D061ChrisCheneytesconet@80.91.229.13","subject":"Re: qgit question: tagged commits not on a branch","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2009-11-27T15:15:06Z","receivedAt":"2009-11-27T15:15:06Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Chris.Cheney venit, vidit, dixit 26.11.2009 22:54:\n> My commit graph has a number of forks (I can't use the word \"branches\" \n> here) that are referenced only by a tag. Whereas gitk --all displays this \n> graph including those forks, qgit does not display those forks - I don't \n> see a way to make it do so, other than by adding branches to those tagged \n> commits. \n> \n> Have I overlooked something?\n> \n\nqgit --all does it for me. It may not be the newest qgit, though.\nI use tags like that to mark a version of a topic branch before\nrebasing, so that on old version won't be gc'ed away and the branch name\nspace is not too crowded. Poor man's topgit, so to say. I guess it's a\ncommon use case.\n\nMichael\n"},{"id":"128577","messageId":"Xns9CD0B0A0076E0ChrisCheneytesconet@80.91.229.13","threadId":"21768","inReplyTo":"4B0FECFA.9040307@drmicha.warpmail.net","subject":"Re: qgit question: tagged commits not on a branch","fromName":"Chris.Cheney","fromEmail":"chris.cheney.nospam@tesco.net","sentAt":"2009-11-27T17:21:33Z","receivedAt":"2009-11-27T17:21:33Z","isPatch":false,"sender":{"key":"chris.cheney.nospam@tesco.net","avatar":null},"body":"Michael J Gruber <git@drmicha.warpmail.net> wrote in\nnews:4B0FECFA.9040307@drmicha.warpmail.net: \n\n> Chris.Cheney venit, vidit, dixit 26.11.2009 22:54:\n>> My commit graph has a number of forks (I can't use the word\n>> \"branches\" here) that are referenced only by a tag. Whereas gitk\n>> --all displays this graph including those forks, qgit does not\n>> display those forks - I don't see a way to make it do so, other than\n>> by adding branches to those tagged commits. \n>> \n>> Have I overlooked something?\n>> \n> \n> qgit --all does it for me. It may not be the newest qgit, though.\n> I use tags like that to mark a version of a topic branch before\n> rebasing, so that on old version won't be gc'ed away and the branch\n> name space is not too crowded. Poor man's topgit, so to say. I guess\n> it's a common use case.\n> \n> Michael\n> \n\nDoh, indeed it does.\n\nThe problem was that qgit isn't (by default) installed in the git program \ndirectory, as is gitk. Ok, I'll need to add a script in the git directory \nto invoke qgit (passing the command-line arguments through) from where it \nresides.\n\n(WIBNI qgit and gitk provided a menu item to switch to --all mode.)\n\nThanks for your help\n\nChris\n"}]}