From: Alejandro Colomar <alx@kernel.org>
To: rajesh <r.pandian@gmail.com>
Cc: Tom Schwindl <schwindl@posteo.de>, linux-man@vger.kernel.org
Subject: Re: [PATCH] bugzilla_218018
Date: Mon, 1 Jan 2024 13:00:38 +0100 [thread overview]
Message-ID: <ZZKpZs1hI_jFHQTg@debian> (raw)
In-Reply-To: <CAKkEDkUEBLbjY-281DWw_0krt_AbGiHvwpHZVu_gxzQKGunL5w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1866 bytes --]
Hi Rajesh,
On Fri, Dec 29, 2023 at 08:49:07AM +0530, rajesh wrote:
> Thanks for the feedback. Have sent it with the subject [PATCH]
> bugzilla_218018_v1
In general, I prefer if versions of patches are sent as replies to the
same mail thread, so I have it more organized in the mailbox. It's not
a big deal, though.
Regarding the subject, the first patch you send is assumed to be v1, so
it's usual to call following ones v2 (v3, ...). Not a big deal here
either, but take it into account for next time. Also,
git-format-patch(1) will do the right thing for you if you pass '-v1' or
'-v2' (or '-vFOO', FWIW) to it.
Cheers,
Alex
>
> On Fri, 29 Dec 2023 at 04:13, Tom Schwindl <schwindl@posteo.de> wrote:
> >
> > Hi,
> >
> > On Thu, Dec 28, 2023 at 09:26:01PM +0530, Rajesh Pandian wrote:
> > > ---
> > > man3/dl_iterate_phdr.3 | 4 +++-
> > > 1 file changed, 3 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/man3/dl_iterate_phdr.3 b/man3/dl_iterate_phdr.3
> > > index 0a8beb3ae..f47fdd502 100644
> > > --- a/man3/dl_iterate_phdr.3
> > > +++ b/man3/dl_iterate_phdr.3
> > > @@ -129,7 +129,9 @@ The
> > > .I dlpi_phnum
> > > field indicates the size of this array.
> > > .P
> > > -These program headers are structures of the following form:
> > > +The ELF program header is described by the type Elf32_Phdr
> > > +or Elf64_Phdr depending on the architecture.
> > > +Following is an example of 32 bit architecture:
> >
> > I'd slightly change the last sentence to
> >
> > The following is an example of the 32-bit architecture
> >
> > since that sounds a bit nicer IMO.
> >
> > > .P
> > > .in +4n
> > > .EX
> > > --
> > > 2.39.2
> > >
> > >
> >
> > --
> > Kind Regards,
> > Tom Schwindl
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-01 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 15:56 [PATCH] bugzilla_218018 Rajesh Pandian
2023-12-28 22:43 ` Tom Schwindl
2023-12-29 3:19 ` rajesh
2024-01-01 12:00 ` Alejandro Colomar [this message]
2024-01-01 11:56 ` Alejandro Colomar
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=ZZKpZs1hI_jFHQTg@debian \
--to=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=r.pandian@gmail.com \
--cc=schwindl@posteo.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.