From: Greg KH <greg@kroah•com>
To: Andrew Klossner <andrew@cesa•opbu.xerox.com>, git@vger•kernel.org
Subject: Re: cannot use stable 2.6.25.y tree with HTTP
Date: Wed, 18 Jun 2008 17:07:22 -0700 [thread overview]
Message-ID: <20080619000722.GA14270@kroah.com> (raw)
In-Reply-To: <200806182037.m5IKboGC012108@pogo.cesa.opbu.xerox.com>
On Wed, Jun 18, 2008 at 01:37:50PM -0700, Andrew Klossner wrote:
> 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 parent reply other threads:[~2008-06-19 0:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806182037.m5IKboGC012108@pogo.cesa.opbu.xerox.com>
2008-06-19 0:07 ` Greg KH [this message]
2008-06-19 0:26 ` cannot use stable 2.6.25.y tree with HTTP Linus Torvalds
2008-06-19 0:58 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080619000722.GA14270@kroah.com \
--to=greg@kroah$(echo .)com \
--cc=andrew@cesa$(echo .)opbu.xerox.com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox