public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: DJ Delorie <dj@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [patch] nss: fix nss_database_lookup2's alternate handling [27416]
Date: Mon, 22 Feb 2021 23:06:16 -0500	[thread overview]
Message-ID: <b04f3979-6ea1-0eb1-4f93-a70b3a32d8a5@redhat.com> (raw)
In-Reply-To: <xnsg5n60tp.fsf@greed.delorie.com>

On 2/22/21 8:16 PM, DJ Delorie wrote:
> "Carlos O'Donell" <carlos@redhat.com> writes:
>> On 2/19/21 5:22 PM, DJ Delorie via Libc-alpha wrote:
>>>
>>> https://sourceware.org/bugzilla/show_bug.cgi?id=27416
>>
>> Could you please provide the full commit message you plan to
>> use for this commit?
> 
> That was it.  Is more required?

The commit message should allow a reviewer to understand the
problem in the briefest form without external reference. A few
sentences about how we got here and why, and what corrective
steps are being taken would be useful for a commit message.

For inspiration please see:
https://sourceware.org/glibc/wiki/Contribution%20checklist#Commit_message_body

A full URL reference to sourceware is also not required.

The subject bug reference should be in one of two forms for
automated processing: (bug xxxx), or [BZ #xxxx]. Please adjust

>> If you commit your change locally then do:
>> git format-patch HEAD~1
>> git send-email mydiff.patch
> 
> I commit my change locally, use gitk to extract it, then mail it on a
> different machine.

That's all OK, you can run git send-email on that remote system if you like
(avoids MUA problems).

https://sourceware.org/glibc/wiki/Contribution%20checklist#Generate_patch

`git format-patch` is the recommended way to get the format that a reviewer 
is expecting.

>> Please repost v2.
> 
> What changes are required?

Please repost v2 with the suggested commit message changes for review.

Reviewing the commit message is part of the review.

When the review is complete the only difference between what is reviewed
and what is committed should be the added Reviewed-by line.
 
>>> +  else if (strcmp (p->pw_name, "name100") != 0)
>>> +    FAIL_EXIT1("getpwuid-compat-test1 name100");
>>
>> OK. Password uses compat which redirects to test1 instead of files.
>> So seeing name100 means files was used and that's wrong.
> 
> "name100" comes from test1; we're testing that it *is* returned, which
> means test1 *is* being used to back compat.

OK.

-- 
Cheers,
Carlos.


  reply	other threads:[~2021-02-23  4:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 22:22 DJ Delorie
2021-02-20 16:19 ` Carlos O'Donell
2021-02-23  1:16   ` DJ Delorie
2021-02-23  4:06     ` Carlos O'Donell [this message]
2021-02-22 12:13 ` Andreas Schwab

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=b04f3979-6ea1-0eb1-4f93-a70b3a32d8a5@redhat.com \
    --to=carlos@redhat.com \
    --cc=dj@redhat.com \
    --cc=libc-alpha@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).