From: Joshua Haberman <joshua@reverberate.org>
To: git@vger.kernel.org
Subject: Re: visualizing Git's Git repo
Date: Tue, 27 May 2008 20:36:16 +0000 (UTC) [thread overview]
Message-ID: <loom.20080527T202009-498@post.gmane.org> (raw)
In-Reply-To: CA563F5A-5E12-42F7-BDFD-04FE3A882028@reverberate.org
Joshua Haberman <joshua <at> reverberate.org> writes:
> 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?
> 2. as a project, why don't you rebase when merging long-running
> branches into master?
Is there really no rationale that anyone can offer for why you do things this
way? I look to Git's own Git repo for best practices, and given Git's emphasis
on "history hygiene" I'm certain that there are reasons for why you do things
the way you do.
Josh
next prev parent reply other threads:[~2008-05-27 20:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 20:47 visualizing Git's Git repo Joshua Haberman
2008-05-26 22:59 ` Eric Hanchrow
2008-05-26 23:42 ` Joshua Haberman
2008-05-26 23:46 ` Shawn O. Pearce
2008-05-27 0:41 ` Björn Steinbrink
2008-05-27 20:36 ` Joshua Haberman [this message]
2008-05-27 23:49 ` Jeff King
2008-05-28 3:15 ` Linus Torvalds
2008-05-28 8:39 ` Jakub Narebski
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=loom.20080527T202009-498@post.gmane.org \
--to=joshua@reverberate.org \
--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;
as well as URLs for NNTP newsgroup(s).