From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 08 Apr 2009 18:51:51 GMT
Subject: Re: [PATCH] perl: add new module Git::Config for cached 'git config' access
Message-ID: <7vtz4zm114.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <49DC736F.1030007@catalyst.net.nz>

Sam Vilain <samv@catalyst.net.nz> writes:

> I'm not quite sure what you want squashed where, maybe just edit the
> below list to be how you'd like it,
>
> pick d43238e perl: add new module Git::Config for cached 'git config' access
> pick 5ea135d perl: make Git.pm use new Git::Config module
> pick b2865bc perl: make Git::Config use --null
> pick 28eecdc perl: fix no value items in Git::Config

For example, if Git::Config is a new thing that this series brings in, and
if the final decision made before the series is integrated into my tree is
that it should read from --null output, then that makes the third one an
"Oops, it was a thinko---I should have used --null from day one" fix-up
that shouldn't be in the resulting series as a separate commit, doesn't
it?  I think the same applies to the last "fix no value 'true' variables"
one.