On Tue, May 27, 2008 at 08:36:16PM +0000, Joshua Haberman wrote:
> > 1. what do you all do to get a high-level view of what's going on with
> > Git development? do you use gitk? if so, what options?
>
> I get the impression from this thread that core Git developers don't make
> visualizing the repository a regular part of their development workflow. Is
> that accurate? What do you all do to keep tabs on Git development?
I don't know if I count as a core Git developer, but I do use gitk daily
to track what goes into Junio's repo. My refs are organized something
like:
remotes/origin/* - tracking branches of Junio's git.git
heads/jk/* - long running topics branched from master
heads/next - Junio's next branch with short or temporary patches on top
My git day generally starts like this:
git fetch ;# grab newly merged stuff
gitk origin/next...next ;# see what's new
git rebase origin/next ;# and bring ourselves up to date
You don't necessarily get to see all of the topic branches labeled
individually, but generally you see each merged topic preceded by the
'Merge ...' commit.
For long running branches, I leave them alone until I'm ready to work on
them. And then it's:
git checkout jk/whatever
gitk origin/master.. ;# what was I doing again?
git rebase origin/master ;# should be clean if nobody else
# is touching the same area
And if the rebase isn't clean, then I investigate individual areas with:
gitk --no-merges jk/whatever...origin/master problematic_file.c
So maybe that is a bit of a boring workflow description, but I do
visualize with gitk all the time. I tend to do a lot of bug-hunting,
too, for which I don't end up doing visualization. Instead, I almost
always rely on asking more specific questions about content: blame
(especially "tig blame"), bisect, and pickaxe ("git log -S").
-Peff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
