From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261441AbVFHRRd (ORCPT ); Wed, 8 Jun 2005 13:17:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261446AbVFHRRc (ORCPT ); Wed, 8 Jun 2005 13:17:32 -0400 Received: from fire.osdl.org ([65.172.181.4]:63710 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261441AbVFHRJu (ORCPT ); Wed, 8 Jun 2005 13:09:50 -0400 Date: Wed, 8 Jun 2005 10:11:33 -0700 (PDT) From: Linus Torvalds To: Paul Mackerras cc: Erik Mouw , Kernel Mailing List , Jeff Garzik Subject: Re: Linux v2.6.12-rc6 In-Reply-To: <17062.21286.601768.751853@cargo.ozlabs.ibm.com> Message-ID: References: <20050607130535.GD16602@harddisk-recovery.com> <17062.21286.601768.751853@cargo.ozlabs.ibm.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 8 Jun 2005, Paul Mackerras wrote: > > This also affects gitk, which takes the first line of the commit > message as the headline. I could make gitk take the first paragraph > (i.e. until the first blank line) as the headline but even that > wouldn't help since you put a blank line between the "Automatic merge" > line and the actual URL. Could you leave out that blank line in > future, or do you have a better suggestion? I'll just make future messages much denser. They should now be just Merge repo or Merge 'name' branch of (and I may decide to replace "branch of" with "from" to make it even denser.) Linus