From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] iw: fix build with new libnl-3
Date: Sat, 24 Dec 2011 16:56:09 +0100 [thread overview]
Message-ID: <4EF5F619.3060906@relinux.de> (raw)
In-Reply-To: <8762h6ouw1.fsf@macbook.be.48ers.dk>
Am 24.12.2011 16:24, schrieb Peter Korsgaard:
>>>>>> "Daniel" == Daniel Mack <zonque@gmail.com> writes:
> >> this file has gone in next. Please rebase your patches on the next
>
> Daniel> I can do this. I wasn't even aware of this branch, and part of the
> Daniel> reason is that it doesn't show up on the cgit web interface
> Daniel> (http://git.buildroot.net/buildroot) when there's no trailing slash in
> Daniel> the URI, which is unfortunately the location the website
> Daniel> (http://buildroot.uclibc.org/git.html) points visitors to. You can click
> Daniel> on "refs" and back on "summary" which will add the "/" suffix, and then
> Daniel> cgit will show the existance of the "next" branch. Very odd.
Even more strange:
http://git.buildroot.net/buildroot
Branch Commit message
Author Age
master <http://git.buildroot.net/buildroot/log/>hostapd: fix libnl
linking with BR2_PREFER_STATIC_LIB
<http://git.buildroot.net/buildroot/commit/>Peter Korsgaard91 min.
manually adding a "/" at the end of the URL gives:
http://git.buildroot.net/buildroot/:
Branch Commit message
Author Age
master <http://git.buildroot.net/buildroot/log/>xapp_xman: fix
dependencies
<http://git.buildroot.net/buildroot/commit/>Peter Korsgaard29 hours
next <http://git.buildroot.net/buildroot/log/?h=next> libroxml: bump
version to 2.1.2
<http://git.buildroot.net/buildroot/commit/?h=next>Tristan Lelong 4 weeks
A nice time to all
Stephan
> Yes, I know. I've reported it to the osuosl.org guys a while back, and
> they are looking into it, but so far without any luck.
>
> I've now fixed the website link.
>
--
reLinux - Stephan Hoffmann
Am Schmidtgrund 124 50765 K?ln
Tel. +49.221.95595-19 Fax: -64
www.reLinux.de sho at reLinux.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20111224/9774ded9/attachment.html>
next prev parent reply other threads:[~2011-12-24 15:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 16:27 [Buildroot] [PATCH] libnl: bump to version 3.2.3 Daniel Mack
2011-11-29 18:16 ` [Buildroot] [PATCH] hostapd: fix build with new libnl-3 Daniel Mack
2011-11-29 18:27 ` Daniel Mack
2011-11-29 18:24 ` [Buildroot] [PATCH] wpa_supplicant: " Daniel Mack
2011-11-29 21:26 ` [Buildroot] [PATCH] libnl: bump to version 3.2.3 Yegor Yefremov
2011-11-29 21:28 ` Yegor Yefremov
2011-11-30 15:05 ` [Buildroot] [PATCH 1/2] iw: fix build with new libnl-3 Daniel Mack
2011-11-30 15:06 ` [Buildroot] [PATCH 2/2] kismet: " Daniel Mack
2011-11-30 15:54 ` [Buildroot] [PATCH 1/2] iw: " Yegor Yefremov
2011-11-30 16:31 ` Daniel Mack
2011-11-30 16:36 ` Michael S. Zick
2011-11-30 16:41 ` Michael S. Zick
2011-11-30 21:31 ` Yegor Yefremov
2011-12-01 11:50 ` Daniel Mack
2011-12-24 15:24 ` Peter Korsgaard
2011-12-24 15:56 ` Stephan Hoffmann [this message]
2011-11-30 15:06 ` [Buildroot] [PATCH] libnl: bump to version 3.2.3 Daniel Mack
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=4EF5F619.3060906@relinux.de \
--to=sho@relinux.de \
--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