From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Subject: gitk screenshots of complex history
Date: Fri, 27 Jul 2007 00:13:01 -0400 [thread overview]
Message-ID: <20070727041300.GD20052@spearce.org> (raw)
I've mentioned both on list and on #git that one of my production
repositories has a few weird points in time. Some folks have asked
to see at least screenshots of the line part of the gitk output,
as apparently they've never seen ugly history in Git. Lucky them.
The images are rather large so I have posted them on my website
with a bit longer explanation of each:
http://www.spearce.org/2007/07/difficult-gitk-graphs.html
I just compared my own history to Linus' linux-2.6 history.
The kernel team can't hold a candle to this mess. Remember,
this is *with* me involved in the project on a daily basis. Me.
Someone who knows Git fairly well...
OK, no more screenshots from *that* repository! I don't ever want
to run `gitk --all` there again. Ever.
PS: The really interesting data (subject lines, authors, dates)
has all been redacted from the images. I can't publish that stuff.
--
Shawn.
next reply other threads:[~2007-07-27 4:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 4:13 Shawn O. Pearce [this message]
2007-07-27 5:20 ` gitk screenshots of complex history Linus Torvalds
2007-07-27 5:29 ` Shawn O. Pearce
2007-07-27 5:49 ` David Kastrup
2007-07-27 13:52 ` Brian Downing
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=20070727041300.GD20052@spearce.org \
--to=spearce@spearce.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).