linux-kernel - Re: [PATCH v3 10/21] backports: avoid git tree reinitialization

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: <1415998051.1847.2.camel@sipsolutions.net>
Date:	Fri, 14 Nov 2014 21:47:31 +0100
From:	Johannes Berg <johannes@...solutions.net>
To:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
Cc:	backports@...r.kernel.org, linux-kernel@...r.kernel.org,
	yann.morin.1998@...e.fr, mmarek@...e.cz, sassmann@...nic.de,
	"Luis R. Rodriguez" <mcgrof@...e.com>
Subject: Re: [PATCH v3 10/21] backports: avoid git tree reinitialization

On Tue, 2014-11-11 at 00:15 -0800, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@...e.com>
> 
> When using backports against for packaging with --gitdebug you either
> have to use --clean or assume the directory is empty already. In either
> case you start fresh. With integration this will be a bit different, you
> could end up with a project directory where the git tree was present but
> only the target directory was empty.
> 
> Calling git init on an already existing git directory will reinitialize
> your git tree, that can reset some config stuff, let's avoid that.

I guess I don't care much, but it seems strange to me that you'd use
--gitdebug in this case, you'd end up committing crappy patches to the
top-level kernel tree?

johannes

--
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/