From: Michael J Gruber <git@drmicha.warpmail.net>
To: "Chris.Cheney" <chris.cheney.nospam@tesco.net>
Cc: git@vger.kernel.org
Subject: Re: qgit question: tagged commits not on a branch
Date: Fri, 27 Nov 2009 16:15:06 +0100 [thread overview]
Message-ID: <4B0FECFA.9040307@drmicha.warpmail.net> (raw)
In-Reply-To: <Xns9CCFDEF02D061ChrisCheneytesconet@80.91.229.13>
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
next prev parent reply other threads:[~2009-11-27 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 21:54 qgit question: tagged commits not on a branch Chris.Cheney
2009-11-27 15:15 ` Michael J Gruber [this message]
2009-11-27 17:21 ` Chris.Cheney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B0FECFA.9040307@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=chris.cheney.nospam@tesco.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox