Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936586AbXJQRjs (ORCPT ); Wed, 17 Oct 2007 13:39:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S936472AbXJQRjd (ORCPT ); Wed, 17 Oct 2007 13:39:33 -0400 Received: from mail1.perex.cz ([212.20.107.53]:59984 "EHLO mail1.perex.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S936465AbXJQRjc (ORCPT ); Wed, 17 Oct 2007 13:39:32 -0400 Date: Wed, 17 Oct 2007 19:39:30 +0200 (CEST) From: Jaroslav Kysela X-X-Sender: perex@tm8103.perex-int.cz To: Linus Torvalds cc: David Miller , linux-kernel@vger.kernel.org, krzysztof.h1@wp.pl Subject: Re: suspicious ALSA empty commit In-Reply-To: Message-ID: References: <20071016.155044.82377336.davem@davemloft.net> 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 Content-Length: 1063 Lines: 33 On Wed, 17 Oct 2007, Linus Torvalds wrote: > On Wed, 17 Oct 2007, Jaroslav Kysela wrote: > > > > I didn't notice, too. I've fixed this commit in my git tree. > > More importantly, how did it get there in the first place? > > As mentioned, normal git tools will not even *allow* you to create an > empty commit by default! So you must be using some really strange workflow > to get an empty commit, or be triggering a git bug, both of which should > be resolved first. I'm using stg on top of git for merging and easy tree rebasing, but the version might be old (I'll try upgrade at first): Stacked GIT 0.12 git version 1.5.0.3 stg import / refresh / pick commands are on way to move patches to linus branch. Jaroslav ----- Jaroslav Kysela Linux Kernel Sound Maintainer ALSA Project - 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/