From: Marcin Cieslak <saper@saper.info>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] procfs.c: Include "filestuff.h"
Date: Wed, 19 Aug 2015 16:52:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.11.1508191651390.7491@z.fncre.vasb> (raw)
In-Reply-To: <864mjv3e97.fsf@gmail.com>
On Wed, 19 Aug 2015, Yao Qi wrote:
> Otherwise, patch is OK to me. You can push it in or I can push it in in
> case you don't have write access to git repository.
Nits should be fixed. It is my first contribution to gdb ever,
so I doubt I have a write access anywhere :)
~Marcin
next prev parent reply other threads:[~2015-08-19 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 18:08 Marcin Cieslak
2015-08-19 7:54 ` Yao Qi
2015-08-19 16:51 ` Marcin Cieslak
2015-08-19 16:52 ` Marcin Cieslak [this message]
2015-08-21 8:21 ` Yao Qi
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=alpine.BSF.2.11.1508191651390.7491@z.fncre.vasb \
--to=saper@saper.info \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@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