From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Is BR's http git repo up-to-date?
Date: Mon, 10 Oct 2011 12:28:59 +0200 [thread overview]
Message-ID: <87r52lcf84.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4E92A9E2.7030300@visionsystems.de> (Yegor Yefremov's message of "Mon, 10 Oct 2011 10:16:34 +0200")
>>>>> "Yegor" == Yegor Yefremov <yegor_sub1@visionsystems.de> writes:
Yegor> Since last week if I execute git pull I always get "Already up-to-date." Even if I clone the http://git.buildroot.net/git/buildroot.git to a new folder my last commit message is
Yegor> commit d1c54ade86e8cae6f0aa1bf1709941c70cea1af7
Yegor> Author: Peter Korsgaard <jacmet@sunsite.dk>
Yegor> Date: Wed Oct 5 00:15:47 2011 +0200
Yegor> imagemagick: add optional fftw support
Yegor> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Yegor> Am I making something wrong?
No, something has gone wrong.
For http access to work, you need to run git update-server-info on the
server to rewrite the refs. We did have a call to git-update-server-info
in hooks/post-update (notice the git-), but the legacy
git-update-server-info symlink is no longer present on the server,
causing it to fail.
Interesting, /usr/bin was updated just around that time, so it is
probably caused by a git upgrade that I wasn't informed about:
drwxr-xr-x 2 root root 36K Oct 4 22:54 .
I've fixed it now, so hopefully it should work in the future. If not,
let me know.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-10-10 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 8:16 [Buildroot] Is BR's http git repo up-to-date? Yegor Yefremov
2011-10-10 10:28 ` Peter Korsgaard [this message]
2011-10-10 10:33 ` Yegor Yefremov
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=87r52lcf84.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.