git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: cannot use stable 2.6.25.y tree with HTTP

From
Greg KH <greg@kroah.com>
Date
Jun 19, 2008, 00:07 UTC
Message-ID
<20080619000722.GA14270@kroah.com>
In-Reply-To
<200806182037.m5IKboGC012108@pogo.cesa.opbu.xerox.com>
On Wed, Jun 18, 2008 at 01:37:50PM -0700, Andrew Klossner wrote:
Show 15 quoted lines
> Hi Greg,
> 
> At the risk of being a pest, I'm following up on my note of last week
> about how the stable-2.6.25.y tree is frozen at 2.6.25.4 when accessed
> via HTTP.  That's the only protocol I can use, and so I cannot pull
> the newer versions.  Is there any hope of fixing this?
> 
> % git pull -v
> >From http://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.25.y
>  = [up to date]      master     -> origin/master
> Already up-to-date.
> 
> % ls .git/refs/tags/v2.6.25.*
> .git/refs/tags/v2.6.25.1  .git/refs/tags/v2.6.25.3
> .git/refs/tags/v2.6.25.2  .git/refs/tags/v2.6.25.4
Argh, this is getting annoying.

git developers, do I need to do something to get git-update-server-info to run on kernel.org every time I do a push so that I don't have to do it by hand (and then forget for new releases, like I did above?)

I thought I remember a script somewhere telling me what to put into a trigger in the git documentation a long time ago.

Oh, wait, is it just:
	chmod +x my-git.git/hooks/post-update
as the core-tutorial.txt file shows?  Is that all that is needed?
thanks,
greg k-h
Next: Linus Torvalds
Message 1 of 3 in “Re: cannot use stable 2.6.25.y tree with HTTP”
  1. Greg KHJun 19, 2008
  2. Linus TorvaldsJun 19, 2008
  3. Greg KHJun 19, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.