unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: bug-hurd@gnu.org, Manolis Ragkousis <manolis837@gmail.com>,
	Samuel Thibault <samuel.thibault@gnu.org>
Cc: guix-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: glibc-2.19-hurd+libpthread-20150515 (was: GSoC: Manolis to work on Guix port to GNU/Hurd)
Date: Fri, 15 May 2015 16:46:43 +0200	[thread overview]
Message-ID: <87fv6xq4oc.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <20150506234305.GU3044@type.youpi.perso.aquilenet.fr>

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

Hi!

On Thu, 7 May 2015 01:43:05 +0200, Samuel Thibault <samuel.thibault@gnu.org> wrote:
> Ludovic Courtès, le Wed 29 Apr 2015 21:40:13 +0200, a écrit :
> > The last missing bit upstream is a libc-for-hurd tarball.
> 
> I have prepared a master-glibc branch in the libpthread repo.

Thanks!  However, shouldn't that just be libpthread's master branch,
nowadays?  (Assuming the idea still is that libpthread is only to be
built as part of glibc's build process?)

> $ git clone git.savannah.gnu.org:/srv/git/hurd/glibc.git/
> $ cd glibc
> $ git checkout tschwinge/Roger_Whittaker
> $ git clone git.savannah.gnu.org:/srv/git/hurd/libpthread.git/
> $ cd libpthread
> $ git checkout master-glibc

> seems to be going fine.  Thomas, can you have a look at uploading a
> tarball of this so it can be used as a base for Guix?

Snapshot uploaded: <http://alpha.gnu.org/gnu/hurd/>, and corresponding
Git tags glibc-2.19-hurd+libpthread-20150515 pushed to the Savannah glibc
and libpthread repositories.


Grüße,
 Thomas

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]

  parent reply	other threads:[~2015-05-15 14:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 19:40 GSoC: Manolis to work on Guix port to GNU/Hurd Ludovic Courtès
2015-04-29 20:18 ` Svante Signell
2015-04-29 21:01 ` Manolis Ragkousis
2015-04-29 21:38   ` Samuel Thibault
2015-04-29 21:53   ` Andreas Enge
2015-04-29 22:15     ` David Thompson
2015-04-30  8:25     ` Ludovic Courtès
2015-04-30  8:27     ` Manolis Ragkousis
2015-04-30 10:39       ` Svante Signell
2015-04-30 10:40         ` A. Fleckenstein
2015-04-30 10:42         ` Taylan Ulrich Bayırlı/Kammer
     [not found] ` <20150506234305.GU3044@type.youpi.perso.aquilenet.fr>
     [not found]   ` <87vbg4r23h.fsf@gnu.org>
     [not found]     ` <20150507151655.GI3348@type>
     [not found]       ` <87bnhwnrjf.fsf@gnu.org>
2015-05-10 20:09         ` Manolis Ragkousis
2015-05-15 14:46   ` Thomas Schwinge [this message]
2015-05-15 14:50     ` glibc-2.19-hurd+libpthread-20150515 (was: GSoC: Manolis to work on Guix port to GNU/Hurd) Samuel Thibault
2015-05-15 16:53     ` glibc-2.19-hurd+libpthread-20150515 Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fv6xq4oc.fsf@kepler.schwinge.homeip.net \
    --to=thomas@codesourcery.com \
    --cc=bug-hurd@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=manolis837@gmail.com \
    --cc=samuel.thibault@gnu.org \
    /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.savannah.gnu.org/cgit/guix.git

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).