All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: gitk screenshots of complex history
Date: Fri, 27 Jul 2007 01:29:34 -0400	[thread overview]
Message-ID: <20070727052934.GH20052@spearce.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0707262219210.3442@woody.linux-foundation.org>

Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Fri, 27 Jul 2007, Shawn O. Pearce wrote:
> > 
> > I just compared my own history to Linus' linux-2.6 history.
> > The kernel team can't hold a candle to this mess.
> 
> Rather on purpose, I might add. I've actually been fairly anal about 
> having people maintain clean histories, to the point where I refuse to 
> pull from trees that don't do a good enough job.

For 4 of our internal repositories I've taken that policy up now
myself, and nobody is allowed to create releases from them except me.
This has helped.  A lot.  So does sensible use of `git rebase -i`.
You and Junio have really sold me on the value of having someone
play a very strict gatekeeper role.  I get better work product from
my coworkers this way too.  They know someone else is looking at
what they are doing and try harder.

But it doesn't help the really old history, nor does it help
the repository these images came from.  I don't own/control that
development.  I just provide git help as much as I can.

-- 
Shawn.

  reply	other threads:[~2007-07-27  5:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27  4:13 gitk screenshots of complex history Shawn O. Pearce
2007-07-27  5:20 ` Linus Torvalds
2007-07-27  5:29   ` Shawn O. Pearce [this message]
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=20070727052934.GH20052@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.