| 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
| ||
|
Message-ID: <4D272D7C.4070900@example.com> Date: Fri, 07 Jan 2011 16:13:00 +0100 From: Piotr Hosowicz <piotr@...owicz.com> To: LKML <linux-kernel@...r.kernel.org> Subject: GIT again Hello, Sorry for bothering again. I think I fimanaged to build the kernel as I wanted to. Lets simplify the problem. There is Linus tree and a separate tree, which was announed here as: git://git.kernel.org/some.git for-linus The objective is to build the kernel with Linus sources with some.git changes incorporatwed in it. I think I managed to achieve the objective doing: # let me remind myself ;-) git clone <Linus URL here> git remote add some git://git.kernel.org/some.git git pull some for-linus I've done it this way and I am convinced I've achieved the objective. But not sure. For sure the last command modified the source, what is what I wanted, I had to finally correct ot by hand and do git commit -a. Am I right? Regards, Piotr Hosowicz -- - Poszedłem wczoraj z żoną do ZOO - I jak? - Nie wzięli... NP: Peter Green Splinter Group - Turn Your Love Away NB: 2.6.37-20110107-1437-pztidm+ -- 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/
Powered by blists - more mailing lists