From: Junio C Hamano <gitster@pobox.com>
To: lukaszgryglicki <lukaszgryglicki@o2.pl>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v3] merge: add a --signoff flag.
Date: Mon, 24 Jul 2017 13:42:46 -0700 [thread overview]
Message-ID: <xmqqr2x5d0s9.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqk22ye2rh.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Mon, 24 Jul 2017 00:02:26 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> lukaszgryglicki <lukaszgryglicki@o2.pl> writes:
>
>> Hi, what is the state of this patch?
>
> I was expecting you to respond to Ævar's <87tw2sbnyl.fsf@gmail.com>
> to explain how your new version addresses his concerns, or him to
> respond to your new patch to say that it addresses his concerns
> adequately. I think neither has happened, so the topic is still in
> limbo, I guess...
Sorry, Ævar's message I meant was <87fueferd4.fsf@gmail.com>.
next prev parent reply other threads:[~2017-07-24 20:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 9:57 [PATCH] area: git-merge: add --signoff flag to git-merge Łukasz Gryglicki
2017-07-03 17:57 ` Junio C Hamano
2017-07-04 6:20 ` [PATCH v2] add --signoff flag to `git-merge` command Łukasz Gryglicki
2017-07-04 8:33 ` Ævar Arnfjörð Bjarmason
2017-07-04 17:42 ` Junio C Hamano
2017-07-04 9:33 ` [PATCH v3] merge: add a --signoff flag Łukasz Gryglicki
2017-07-24 6:14 ` lukaszgryglicki
2017-07-24 7:02 ` Junio C Hamano
2017-07-24 20:42 ` Junio C Hamano [this message]
2017-07-25 5:00 ` lukaszgryglicki
2017-07-25 5:10 ` Stefan Beller
2017-07-25 11:28 ` lukaszgryglicki
2017-07-25 18:41 ` Junio C Hamano
[not found] ` <7A9ED766-4A25-4F34-8E02-3DFCE1D63ADF@o2.pl>
2017-07-26 7:34 ` Junio C Hamano
2017-07-26 7:39 ` [PATCH v4] " Łukasz Gryglicki
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=xmqqr2x5d0s9.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=lukaszgryglicki@o2.pl \
/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).