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 for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <452D3DFA.6010408@tls.msk.ru>
Date:	Wed, 11 Oct 2006 22:54:50 +0400
From:	Michael Tokarev <mjt@....msk.ru>
To:	Linux-kernel <linux-kernel@...r.kernel.org>
Subject: [SOT] GIT usage question

For quite some time I'm trying to understand if it's possible
to extract changes from some subsystem's GIT tree compared to
some version of linux kernel.

For example, let's say I want to see if my SATA controller will
work with current libata, but without all the pain of trying
current 2.6.19-pre/rc instabilities.  Libata changes are quite
local for the subsystem, so in theory, or at least how I see
it, that should be possible.

So I have 3 remote branches in my local GIT tree:

 o origin which points to Linus's 2.6.19-pre
 o libata, which is current libata tree
 o 2.6.18 release -- the kernel I'm running right now.

I want to get changes *for libata subsystem* in origin or
libata (libata is just changes which are on the way to Linus,
and current difference is very minor), to apply against 2.6.18.
Ie, in short, changes which went to origin *from* libata.

Is it possible?

Thanks.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ