Re: [BUG] gitweb on repo.or.cz shows buggy commitdiff

From: Petr Baudis <pasky@suse.cz>
Date: Aug 27, 2007, 00:48 UTC
Message-ID: <20070827004838.GO1219@pasky.or.cz>
In-Reply-To: <200708270230.04537.jnareb@gmail.com>

On Mon, Aug 27, 2007 at 02:30:04AM CEST, Jakub Narebski wrote:

Show 14 quoted lines

> 2. Alternate solution is to note that we have split patch only in the case
> of 'T' (type change) status, and for typechange we always split patch in
> two, so there are two patches corresponding to single raw diff-tree line.
> 
> So it would be enough to introduce $continued_patch variable, unset it
> after writing that patch is continued if it is true, set it to true if
> there was typechange, i.e. if status (one of status) is 'T'.
> 
> And we can get rid of buffering extended diff header and parsing it,
> I think. This would simplify git_patchset_body, making it easier to
> understand and maintain.
> 
> But this depends on my understanding on "git diff-tree --patch-with-raw"
> output, and that it would not change in the future WRT split patches.

I'd prefer this solution, though I think split patch could also happen if you use -B (which I think is very good idea to use and it's a pity that it isn't default - or is it?).

-- 
				Petr "Pasky" Baudis
Early to rise and early to bed makes a male healthy and wealthy and dead.
                -- James Thurber