From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] HTTP access to git repository outdated
Date: Mon, 25 Aug 2014 16:11:20 +0200 [thread overview]
Message-ID: <87y4ucveuv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20140825160033.08334f2d@free-electrons.com> (Thomas Petazzoni's message of "Mon, 25 Aug 2014 16:00:33 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Dear Baruch Siach,
> On Mon, 25 Aug 2014 13:53:29 +0300, Baruch Siach wrote:
>> On Mon, Aug 25, 2014 at 12:51:19PM +0200, Richard Braun wrote:
>> > It looks like git update-server-info isn't run automatically since
>> > getting the repository through http gives a slightly outdated tree.
>>
>> This is a known problem. Try adding or removing the trailing slash from the
>> git repository URL.
> Completely separate issue.
> The problem with the http/git difference is that when I push some
> changes to the official repository, git update-server-info is not
> executed due to some permission issues. So the http side of things only
> gets resynced the next time Peter pushes something.
> Since I'm the last one to have pushed some stuff.
> The last commit available from the http:// repo was pushed by Peter
> (f67e7ba06f5f00dc9153ad364932092692458704 package/gutenprint: replaces
> -static with -static-libtool-libs).
I'll have a look at the permission issue / notify the osuosl guys so
this gets fixed.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2014-08-25 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 10:51 [Buildroot] HTTP access to git repository outdated Richard Braun
2014-08-25 10:53 ` Baruch Siach
2014-08-25 11:13 ` Richard Braun
2014-08-25 11:51 ` Mike Zick
2014-08-25 12:58 ` Thomas De Schampheleire
2014-08-25 14:00 ` Thomas Petazzoni
2014-08-25 14:11 ` Peter Korsgaard [this message]
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=87y4ucveuv.fsf@dell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox