qgit question: tagged commits not on a branch

qgit question: tagged commits not on a branch

[Chris.Cheney]

My commit graph has a number of forks (I can't use the word "branches" 
here) that are referenced only by a tag. Whereas gitk --all displays this 
graph including those forks, qgit does not display those forks - I don't 
see a way to make it do so, other than by adding branches to those tagged 
commits. 

Have I overlooked something?

TIA

Chris

Re: qgit question: tagged commits not on a branch

[Michael J Gruber]

Chris.Cheney venit, vidit, dixit 26.11.2009 22:54:
> My commit graph has a number of forks (I can't use the word "branches" 
> here) that are referenced only by a tag. Whereas gitk --all displays this 
> graph including those forks, qgit does not display those forks - I don't 
> see a way to make it do so, other than by adding branches to those tagged 
> commits. 
> 
> Have I overlooked something?
> 

qgit --all does it for me. It may not be the newest qgit, though.
I use tags like that to mark a version of a topic branch before
rebasing, so that on old version won't be gc'ed away and the branch name
space is not too crowded. Poor man's topgit, so to say. I guess it's a
common use case.

Michael

Re: qgit question: tagged commits not on a branch

[Chris.Cheney]

Michael J Gruber <git@drmicha.warpmail.net> wrote in
news:4B0FECFA.9040307@drmicha.warpmail.net: 

> Chris.Cheney venit, vidit, dixit 26.11.2009 22:54:
>> My commit graph has a number of forks (I can't use the word
>> "branches" here) that are referenced only by a tag. Whereas gitk
>> --all displays this graph including those forks, qgit does not
>> display those forks - I don't see a way to make it do so, other than
>> by adding branches to those tagged commits. 
>> 
>> Have I overlooked something?
>> 
> 
> qgit --all does it for me. It may not be the newest qgit, though.
> I use tags like that to mark a version of a topic branch before
> rebasing, so that on old version won't be gc'ed away and the branch
> name space is not too crowded. Poor man's topgit, so to say. I guess
> it's a common use case.
> 
> Michael
> 

Doh, indeed it does.

The problem was that qgit isn't (by default) installed in the git program 
directory, as is gitk. Ok, I'll need to add a script in the git directory 
to invoke qgit (passing the command-line arguments through) from where it 
resides.

(WIBNI qgit and gitk provided a menu item to switch to --all mode.)

Thanks for your help

Chris