public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: svante.signell@gmail.com
Cc: Samuel Thibault <samuel.thibault@gnu.org>,
	bug-hurd <bug-hurd@gnu.org>,
		Debian GCC Maintainers <debian-gcc@lists.debian.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: Hurd port for gcc go PATCH 1-4(23)
Date: Thu, 08 Dec 2016 00:16:00 -0000	[thread overview]
Message-ID: <CAKOQZ8zPo5tgsu5BjEPLKRoMgAD2Gp7qtNoZYTPSdSXG1h3hkQ@mail.gmail.com> (raw)
In-Reply-To: <1481148146.9077.36.camel@gmail.com>

On Wed, Dec 7, 2016 at 2:02 PM, Svante Signell <svante.signell@gmail.com> wrote:
>
> I'm sorry but neither of you or I are in the position to request changes of
> already existing file names e.g. replacing linux with glibc in:
> os/pipe_linux.go
> crypto/x509/root_linux.go
> syscall/errstr_linux.go

As you know, the name "linux" in those files means that the files are
only compiled on GNU/Linux systems.  The files in os and crypto are
copied from the master library in the gc repository.  Those names are
not going to change.  The file syscall/errstr_linux.go is specific to
gccgo, and that name could change easily enough.

> Neither are we in the position to request to rename libcall_posix.go to
> something else, or move the four functions definitions mount, mlocall,
> munlockall, madvise, mentioned above to a separate file.

Making those changes is fine.

> So far, nobody, upstream or debian-gcc, have made any comment on the patches
> whatsoever. So what are we doing? Let's forget about porting gccgo to GNU/Hurd.

Yes, I'm sorry that this never gets high enough on my list for a serious review.

The best way to contribute to gccgo is to use the process described at
https://golang.org/doc/gccgo_contribute.html.  That explains how to
send changes to Gerrit in a way that is easy for me to review and
apply (Gerrit is itself free software).  You are much more likely to
get a response if you are able to follow that approach.

Ian

  reply	other threads:[~2016-12-08  0:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161126231752.GH2658@var.home>
     [not found] ` <1480264432.24382.154.camel@gmail.com>
2016-11-27 17:02   ` Samuel Thibault
2016-11-27 17:17     ` Svante Signell
2016-11-27 17:22       ` Samuel Thibault
2016-12-07 13:52     ` Svante Signell
2016-12-07 14:08       ` Samuel Thibault
2016-12-07 14:32         ` Svante Signell
2016-12-07 16:25           ` Samuel Thibault
2016-12-07 22:02             ` Svante Signell
2016-12-08  0:16               ` Ian Lance Taylor [this message]
2016-11-25 19:57 Svante Signell
2016-12-18 23:40 ` Samuel Thibault
2016-12-19  5:52   ` Samuel Thibault

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=CAKOQZ8zPo5tgsu5BjEPLKRoMgAD2Gp7qtNoZYTPSdSXG1h3hkQ@mail.gmail.com \
    --to=iant@google.com \
    --cc=bug-hurd@gnu.org \
    --cc=debian-gcc@lists.debian.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=samuel.thibault@gnu.org \
    --cc=svante.signell@gmail.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.
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).