mailing list of musl libc
 help / color / mirror / code / Atom feed
From: stephen Turner <stephen.n.turner@gmail.com>
To: musl@lists.openwall.com
Subject: Re: musl-llvm-clang-libc++
Date: Tue, 6 Jan 2015 11:41:06 -0500	[thread overview]
Message-ID: <CAA7aPHgBGyOKsxyHyF+c=3BKx9n6pHn97E3fPVKtV_-rok5kpA@mail.gmail.com> (raw)
In-Reply-To: <54ABF9E8.1070105@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

>
> Probably it is time to get all the information in a single place, it
> isn't the first time somebody succeeds but I always see scattered
> information.
>
> lu
>
>
I dont use clang but i would imagine if patches aren't available then
people would be asking for them soon. It might be nice to have all patches
hosted in one location too that doesn't serialize the web link making wget
difficult on a cli only system. The gregorr musl link typically does this
long serialized connection. what makes it worse is you cant script it
because the link changes from time to time.

example
https://bitbucket.org/GregorR/musl-cross/raw/69ea1932e1a8bb172c0a159dfceb70f822fc71d2/build.sh

thanks,
stephen

[-- Attachment #2: Type: text/html, Size: 1299 bytes --]

  reply	other threads:[~2015-01-06 16:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 14:31 musl-llvm-clang-libc++ Tomasz Sterna
2015-01-06 14:55 ` musl-llvm-clang-libc++ Daniel Cegiełka
2015-01-06 15:06 ` musl-llvm-clang-libc++ Luca Barbato
2015-01-06 16:41   ` stephen Turner [this message]
2015-01-06 16:43 ` musl-llvm-clang-libc++ Szabolcs Nagy
2015-01-06 17:29   ` musl-llvm-clang-libc++ Szabolcs Nagy
2015-01-06 17:50   ` musl-llvm-clang-libc++ Rich Felker
2015-01-06 22:12 ` musl-llvm-clang-libc++ Richard Pennington
2015-01-06 23:43   ` musl-llvm-clang-libc++ Tomasz Sterna
2015-01-07  0:26     ` musl-llvm-clang-libc++ Richard Pennington

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='CAA7aPHgBGyOKsxyHyF+c=3BKx9n6pHn97E3fPVKtV_-rok5kpA@mail.gmail.com' \
    --to=stephen.n.turner@gmail.com \
    --cc=musl@lists.openwall.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).