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 -- 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
