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] [day] [month] [year] [list]
Date:	Sat, 14 Jul 2007 21:40:37 +0200
From:	Francois Romieu <>
To:	Jonathan Larsen <>
Subject: Re: Fwd: r8169 driver supporting the 8167 dev ID

Jonathan Larsen <> :
> >You should read the tutorial until you find the 'Using git for 
> >collaboration'
> >part. You missed a:
> >
> >git clone 
> >git://
> Alright sweet, i got somewhere :).  i was able to pull that down, do
> my previous steps and git commit  and then the git format patch and it
> pulled down a whole bunch of .patch files.
> i've seen them before.  they also exist here.
> Im confused as what i would need to do with these files.  would i run
> them as a patch against the r8169.c file?  ie: patch p1 < 'one of the
> patch files.patch'?
> the other thing i've ran into trouble with is getting the git kernel
> version for  i've searched for a file and
> haven't seen anything and also tried using get pull v2.6.16.52 and i
> get a fatal error.  unable to chdir or not a git archive.  i've also
> tried without the .52 and get the same thing.

In the clone directory, try:
$ git remote add 2.6.16.y git://
$ git remote fetch 2.6.16.y
$ git checkout -f v2.6.16.52

You are strongly urged to RTFM to figure what the commands above (and
below) do.

>From here you apply each of the patches which are in the current 'master'
branch but not in the 2.6.16.y branch at v2.6.16.52. You can play with
'git merge-base' and 'git format-patch' to see the flow of r8169 patches
in both branches but there are surely more elaborate tools/commands.

Use 'git am' to apply the patches. The ordering should guide you.
If a patch apply, go on to the compilation step. If the patch does not
apply, you can force it by hand, fix the rejects and add the missing
files until it compiles. 'git {add/update-index}' the added/updated
files and issue 'git am --resolved'. Save the commit somewhere, it
could be useful. If the patch applied but did not compile, you can
'git reset --hard HEAD^', patch -p1, git {add/update-index} and git
commit by hand.

Repeat until illumination.

> i just want to make sure it was understood that i want try and make
> the r8169 driver that supported my card in 2.6.22 and back port it to
> work in

If 2.6.22 works for you, fine. You could be interested by the post 2.6.22
r8169 patches though.

If you have more questions related to git which are not answered in the man
pages, you should ask them in the git mailing list (

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists