Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751448AbWEDJFe (ORCPT ); Thu, 4 May 2006 05:05:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751451AbWEDJFd (ORCPT ); Thu, 4 May 2006 05:05:33 -0400 Received: from w241.dkm.cz ([62.24.88.241]:31404 "EHLO machine.or.cz") by vger.kernel.org with ESMTP id S1751448AbWEDJFd (ORCPT ); Thu, 4 May 2006 05:05:33 -0400 Date: Thu, 4 May 2006 11:06:31 +0200 From: Petr Baudis To: Junio C Hamano Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: What's in git.git Message-ID: <20060504090631.GV27689@pasky.or.cz> References: <7vbque5hq9.fsf@assigned-by-dhcp.cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7vbque5hq9.fsf@assigned-by-dhcp.cox.net> X-message-flag: Outlook : A program to spread viri, but it can do mail too. User-Agent: Mutt/1.5.11 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1086 Lines: 25 Dear diary, on Thu, May 04, 2006 at 10:14:54AM CEST, I got a letter where Junio C Hamano said that... > - core.prefersymlinkrefs can be given to use symlink HEAD; > this may be needed to bisect kernel history before January > 2006 whose setlocalversion script depended on HEAD being a > symlink. Oh, I expected this to end up in 1.3.2, actually. :-) Shouldn't this belong to the maint branch? It is "physically" a new feature but I would consider "cannot bisect kernel before January" a bug certainly worth fixing and the feature is pretty tiny. (It seems to be backwards-incompatible but that only means you should provide some transition path, I think. ;) -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ Right now I am having amnesia and deja-vu at the same time. I think I have forgotten this before. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/