From: Joseph Strauss <josephst@bhphoto.com>
To: Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: RE: Bug With git rebase -p
Date: Thu, 22 Mar 2018 16:47:32 +0000 [thread overview]
Message-ID: <e1f49e12af544f4c9ece2794f7be4d9a@EXMBX02B.bhphotovideo.local> (raw)
In-Reply-To: <xmqqd0zwm5fd.fsf@gitster-ct.c.googlers.com>
I meant to say that I installed 2.17.0-rc0, and it worked perfectly. Sorry for the ambiguity.
-----Original Message-----
From: Junio C Hamano [mailto:jch2355@gmail.com] On Behalf Of Junio C Hamano
Sent: Thursday, March 22, 2018 12:39 PM
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Joseph Strauss <josephst@bhphoto.com>; git@vger.kernel.org
Subject: Re: Bug With git rebase -p
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> On Tue, 20 Mar 2018, Joseph Strauss wrote:
>
>> Perfect. Thank you.
>
> You are welcome.
>
> I am puzzled, though... does your message mean that you tested the Git
> for Windows v2.17.0-rc0 installer and it did fix your problem? Or do
> you simply assume that it does fix your problem because Junio & I
> expect it to fix your problem?
Thanks for asking, as I was curious about the same thing after interpreting what Joseph said as "oh, perfect that there is a packaged thing I can readily test" (implying "I'll get back to you after seeing if it helps").
next prev parent reply other threads:[~2018-03-22 16:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 20:23 Bug With git rebase -p Joseph Strauss
2018-03-19 20:53 ` Junio C Hamano
2018-03-20 14:52 ` Johannes Schindelin
2018-03-20 15:18 ` Joseph Strauss
2018-03-21 22:33 ` Johannes Schindelin
2018-03-22 16:38 ` Junio C Hamano
2018-03-22 16:47 ` Joseph Strauss [this message]
2018-03-23 9:39 ` 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=e1f49e12af544f4c9ece2794f7be4d9a@EXMBX02B.bhphotovideo.local \
--to=josephst@bhphoto.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).