git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: M Hickford via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org,
	Matthew John Cheetham <mjcheetham@outlook.com>,
	M Hickford <mirth.hickford@gmail.com>
Subject: Re: [PATCH v4 0/2] credential: improvements to erase in helpers
Date: Thu, 15 Jun 2023 17:21:16 -0400	[thread overview]
Message-ID: <20230615212116.GA39325@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqh6r8v3es.fsf@gitster.g>

On Thu, Jun 15, 2023 at 02:09:15PM -0700, Junio C Hamano wrote:

> "M Hickford via GitGitGadget" <gitgitgadget@gmail.com> writes:
> 
> > M Hickford (2):
> >   credential: avoid erasing distinct password
> >   credential: erase all matching credentials
> >
> >  Documentation/git-credential.txt   |   2 +-
> >  Documentation/gitcredentials.txt   |   2 +-
> >  builtin/credential-cache--daemon.c |  17 +++--
> >  builtin/credential-store.c         |  15 +++--
> >  credential.c                       |   7 +-
> >  credential.h                       |   2 +-
> >  t/lib-credential.sh                | 103 +++++++++++++++++++++++++++++
> >  7 files changed, 128 insertions(+), 20 deletions(-)
> 
> It is helpful to reviewers to describe/summarize, in your own words,
> what changed since the previous version, in the cover letter.
> 
> The range-diff generated for the versions can serve as a good
> supporting material, and it would help you while writing that
> summary, but not a substitute for the summary.

Yeah, I agree that would have made reviewing much easier. :)

That said, I just re-reviewed the patches themselves, and everything now
looks good to me.

-Peff

  reply	other threads:[~2023-06-15 21:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 11:23 [PATCH 0/2] credential: improvements to erase in helpers M Hickford via GitGitGadget
2023-06-14 11:23 ` [PATCH 1/2] credential: avoid erasing distinct password M Hickford via GitGitGadget
2023-06-14 11:23 ` [PATCH 2/2] credential: erase all matching credentials M Hickford via GitGitGadget
2023-06-14 16:00   ` Junio C Hamano
2023-06-14 21:35     ` M Hickford
2023-06-14 21:40 ` [PATCH v2 0/2] credential: improvements to erase in helpers M Hickford via GitGitGadget
2023-06-14 21:40   ` [PATCH v2 1/2] credential: avoid erasing distinct password M Hickford via GitGitGadget
2023-06-14 22:43     ` Jeff King
2023-06-15  4:51       ` M Hickford
2023-06-14 21:40   ` [PATCH v2 2/2] credential: erase all matching credentials M Hickford via GitGitGadget
2023-06-14 22:51     ` Jeff King
2023-06-15  4:57       ` M Hickford
2023-06-14 21:56   ` [PATCH v2 0/2] credential: improvements to erase in helpers Junio C Hamano
2023-06-14 22:51     ` Jeff King
2023-06-15  6:03   ` [PATCH v3 " M Hickford via GitGitGadget
2023-06-15  6:03     ` [PATCH v3 1/2] credential: avoid erasing distinct password M Hickford via GitGitGadget
2023-06-15  7:08       ` Jeff King
2023-06-15  6:03     ` [PATCH v3 2/2] credential: erase all matching credentials M Hickford via GitGitGadget
2023-06-15  7:09       ` Jeff King
2023-06-15 19:19     ` [PATCH v4 0/2] credential: improvements to erase in helpers M Hickford via GitGitGadget
2023-06-15 19:19       ` [PATCH v4 1/2] credential: avoid erasing distinct password M Hickford via GitGitGadget
2023-06-15 19:19       ` [PATCH v4 2/2] credential: erase all matching credentials M Hickford via GitGitGadget
2023-06-15 21:09       ` [PATCH v4 0/2] credential: improvements to erase in helpers Junio C Hamano
2023-06-15 21:21         ` Jeff King [this message]
2023-06-15 21:52           ` Junio C Hamano
2023-06-16 16:54           ` Junio C Hamano

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=20230615212116.GA39325@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=gitster@pobox.com \
    --cc=mirth.hickford@gmail.com \
    --cc=mjcheetham@outlook.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 NNTP newsgroup(s).