public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roland at gnu dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug admin/13933] New: web site links to git are not so easy to find Date: Sat, 31 Mar 2012 03:17:00 -0000 [thread overview] Message-ID: <bug-13933-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13933 Bug #: 13933 Summary: web site links to git are not so easy to find Product: glibc Version: unspecified Status: NEW Severity: minor Priority: P2 Component: admin AssignedTo: unassigned@sourceware.org ReportedBy: roland@gnu.org CC: carlos@systemhalted.org, roland@gnu.org Classification: Unclassified I happened to be someplace where only a browser was handy and wanted to look at some libc source. I started on the web page, hit the Development tab, and was quite flummoxed when I could see any links to the repositories there. It wasn't until after I'd given up and just guessed that sourceware.org/git would work as a starting place (it does) that it occurred to me to look for them on the Download page. Usually live source repository references are under Development while only canned tarballs are under Download. With the tab structure, it might actually be easiest to have a "Sources" tab with that info for quick navigation. But certainly the Development page should contain a link to somewhere with that info, if not the info itself. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-03-31 2:23 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-31 3:17 roland at gnu dot org [this message] 2012-03-31 21:00 ` [Bug admin/13933] " carlos_odonell at mentor dot com 2012-04-02 18:28 ` roland at gnu dot org 2012-12-03 23:52 ` carlos at systemhalted dot org 2012-12-03 23:54 ` carlos at systemhalted dot org 2014-06-25 11:24 ` fweimer at redhat dot com
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=bug-13933-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).