linux-kernel - Re: suspicious ALSA empty commit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0710171928250.11118@tm8103.perex-int.cz>
Date:	Wed, 17 Oct 2007 19:39:30 +0200 (CEST)
From:	Jaroslav Kysela <perex@...ex.cz>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
cc:	David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org,
	krzysztof.h1@...pl
Subject: Re: suspicious ALSA empty commit

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 <perex@...ex.cz>
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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/