linux-kernel - Re: Linux 2.6.22.1

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: <alpine.LFD.0.999.0707122328340.20061@woody.linux-foundation.org>
Date:	Thu, 12 Jul 2007 23:34:50 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Bryan Wu <bryan.wu@...log.com>
cc:	Greg KH <greg@...ah.com>, Chris Wright <chrisw@...s-sol.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>, stable@...nel.org,
	Nish Aravamudan <nish.aravamudan@...il.com>
Subject: Re: Linux 2.6.22.1

On Fri, 13 Jul 2007, Bryan Wu wrote:
> 
> I can git-pull from Linus tree through http in my company, this one
> can't. If it is not easy to open it by you guys, I have to git-pull at
> home, -:))

In that case, it's almost certainly that that tree isn't doing the proper 
"git update-server-info" when people push to it.

Chris/Greg: just add a

	hooks/post-update

file to your git repo that is executable, and just contains

	#!/bin/sh
	exec git-update-server-info

in it, and you'll be golden. It will mean that every time you push to the 
repo, it will run the "git update-server-info" thing after the push. And 
that will update all the necessary files for the stupid protocols (ie 
http) that don't know about git natively.

Oh, and run the "git-update-server-info" once by hand, just so that you 
don't then have to wait until after the next push for the git repo to be 
accessible by http://

www.kernel.org serves git repos fine, but the git repos have to help a bit 
at doing so.

What git update-server-info does is to create "info/refs" and 
"objects/info/packs" files that contain enough information for a client to 
figure out what refs and pack objects exist, so that they can try to fetch 
the necessary data on their own.

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