From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] iw: fix build with new libnl-3
Date: Wed, 30 Nov 2011 10:36:38 -0600 [thread overview]
Message-ID: <201111301036.41643.minimod@morethan.org> (raw)
In-Reply-To: <4ED65A6C.2020003@gmail.com>
On Wed November 30 2011, Daniel Mack wrote:
> I can do this. I wasn't even aware of this branch, and part of the
> reason is that it doesn't show up on the cgit web interface
> (http://git.buildroot.net/buildroot) when there's no trailing slash in
> the URI, which is unfortunately the location the website
> (http://buildroot.uclibc.org/git.html) points visitors to. You can click
> on "refs" and back on "summary" which will add the "/" suffix, and then
> cgit will show the existance of the "next" branch. Very odd.
>
Confirmed here also.
Just adding the "/" to the URI in the browser bar and hitting "enter"
fixes the display of the "next" branch also.
Mike
next prev parent reply other threads:[~2011-11-30 16:36 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 [this message]
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
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=201111301036.41643.minimod@morethan.org \
--to=minimod@morethan.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