public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@moxielogic.com>
To: bin.xu@cs2c.com.cn
Cc: libffi-discuss <libffi-discuss@sourceware.org>
Subject: Re: About libffi support Sunway CPU sw_64 arch platform
Date: Thu, 16 Aug 2018 13:06:00 -0000	[thread overview]
Message-ID: <CACxje58s9QdaUnxZtsNkbMWRGyQLkRbDi-10YFP4uirZw43stg@mail.gmail.com> (raw)
In-Reply-To: <2018081609423989774810@cs2c.com.cn>

Hi,

  We use github to manage libffi. https://github.com/libffi/libffi

  The easiest way to submit a patch is to get a github account , fork the
libffi project, commit and push your changes to github, then create a Pull
Request back to the original project

AG

On Wed., Aug. 15, 2018, 9:43 p.m. bin.xu@cs2c.com.cn, <bin.xu@cs2c.com.cn>
wrote:

> Hi,We want to contribute the patch for support Sunway CPU sw_64 arch
> platform,Do you guilde us the process about submit the patch? thanks!
>
>
>
> bin.xu@cs2c.com.cn
>

      reply	other threads:[~2018-08-16 13:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16  1:42 bin.xu
2018-08-16 13:06 ` Anthony Green [this message]

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=CACxje58s9QdaUnxZtsNkbMWRGyQLkRbDi-10YFP4uirZw43stg@mail.gmail.com \
    --to=green@moxielogic.com \
    --cc=bin.xu@cs2c.com.cn \
    --cc=libffi-discuss@sourceware.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.
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).