public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: ricaljasan <ricaljasan@pacific.net>
To: Siddhesh Poyarekar <siddhesh@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Preferred Format of GNU C Library Manual Edits
Date: Thu, 09 Jul 2015 02:25:00 -0000	[thread overview]
Message-ID: <559DDBD3.4030607@pacific.net> (raw)
In-Reply-To: <20150707072427.GJ13549@spoyarek.pnq.redhat.com>

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

On 07/07/2015 12:24 AM, Siddhesh Poyarekar wrote:
> If you
> separate the two and then ensure that your patches are not too large
> (something as simple as one patch per file is also good enough), I
> think you would have done enough to make it easy for your reviewers.

Thank you for the feedback.  That should be exactly how things work out,
as each chapter is typically a single file.  There may be supplementary
files which have a few additional edits, but many of the included files
are code examples and I have example vetting set aside as a separate
project.

>> Getting to the actual patch submission part of this, the way I plan on
>> doing it is something like:
>> 
>> [Patch M/N] Grammatical edits to the GNU C Library Reference Manual.
>> 
>> where each M is a chapter.  Variable formatting and other manual-wide
>> topics would follow similarly.

Rical


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2015-07-09  2:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 10:53 ricaljasan
2015-07-07  7:24 ` Siddhesh Poyarekar
2015-07-09  2:25   ` ricaljasan [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=559DDBD3.4030607@pacific.net \
    --to=ricaljasan@pacific.net \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@redhat.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).