From: Junio C Hamano <gitster@pobox.com>
To: Andrey <ahippo@yandex.ru>
Cc: Luke Diamand <luke@diamand.org>,
"Philip.McGraw" <philip.mcgraw@bentley.com>,
Lars Schneider <larsxschneider@gmail.com>,
Git Users <git@vger.kernel.org>,
Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>
Subject: Re: [PATCH v2 1/1] git-p4: auto-delete named temporary file
Date: Sun, 6 Oct 2019 11:43:01 +0900 [thread overview]
Message-ID: <CAPc5daXU=fcjYJ4p6wQH-Ljz1Y8j=sBiwcN96hkxhP4CP_k8uA@mail.gmail.com> (raw)
In-Reply-To: <10209481570324845@myt6-4218ece6190d.qloud-c.yandex.net>
> >> ...
> >> Luke, does this look good?
> >>
> >> I know Mazo is the only other contributor who has multiple commits
> >> to git-p4.py in the past 2 years, to make Reviewed-by carry some
> >> weight ;-) but as we have so small number of people touching this
> >> script anyway, I'd rather see what the main contributor in the past
> >> 2 years thinks.
> >
> > I think it looks reasonable.
> >
> > Ack.
>
> Junio, does Philip need to resend a v3 with Luke's ack or will you just add it yourself while queuing the patch?
> (sorry, if you already picked up the patch -- I just didn't see it in the last What's cooking update)
Sorry, I do not recall the details of this old a thread but if I
recall correctly there was only a corrupt patch that I cannot use,
so somebody would need to send a patch that actually applies. With a
patch that applies, I can tweak the log message
with acked-by etc. just fine.
Thanks.
next prev parent reply other threads:[~2019-10-06 2:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 21:39 [PATCH 0/1] git-p4: auto-delete named temporary file Philip McGraw via GitGitGadget
2019-08-02 3:48 ` Andrey
2019-08-02 19:43 ` [PATCH v2 " Philip McGraw via GitGitGadget
2019-08-27 3:43 ` [PATCH v2 1/1] " Andrey Mazo
2019-08-27 22:31 ` Junio C Hamano
2019-08-28 8:34 ` Luke Diamand
[not found] ` <10209481570324845@myt6-4218ece6190d.qloud-c.yandex.net>
2019-10-06 2:43 ` Junio C Hamano [this message]
2019-08-26 13:51 ` [PATCH " Git Gadget
2019-08-26 16:39 ` Junio C Hamano
2019-08-28 12:25 ` Johannes Schindelin
2019-08-29 3:57 ` Junio C Hamano
2019-08-29 11:45 ` Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPc5daXU=fcjYJ4p6wQH-Ljz1Y8j=sBiwcN96hkxhP4CP_k8uA@mail.gmail.com' \
--to=gitster@pobox.com \
--cc=ahippo@yandex.ru \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=larsxschneider@gmail.com \
--cc=luke@diamand.org \
--cc=philip.mcgraw@bentley.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).