From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Wink Saville <wink@saville.com>
Cc: Paul Sebastian Ungureanu <ungureanupaulsebastian@gmail.com>,
Git List <git@vger.kernel.org>
Subject: Re: [GSoC] Regarding "Convert scripts to builtins"
Date: Thu, 22 Mar 2018 18:32:11 +0100 (STD) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1803221831120.77@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz> (raw)
In-Reply-To: <CAKk8isrOMMm0zyJ1JtH3aDm=tF5hwokZ0Wzn=D1BQ1R-qEPicw@mail.gmail.com>
Hi Wink,
On Wed, 21 Mar 2018, Wink Saville wrote:
> I plead guilty to being the preson refactoring --preserve-merges. But
> after reading this and seeing that --recreate-merges is coming and
> possibly git-rebase--* moving to C I'm worried I'd be messing things up.
Don't worry. We will just work together to avoid messing anything up.
> Also, Eric Sunshine felt my v1 changes causes the blame information to
> be obscured. So I created a v2 change which keeps everything in the
> git-rebase--interactive.sh.
Great!
> Please see "[RFC PATCH 0/3] rebase-interactive" and
> "[RFC PATCH v2 0/1] rebase-interactive: ...". I'm looking for
> advice on how to proceed.
Sadly, I had almost no time to spend on the Git mailing list today, but I
will have a look tomorrow, okay?
Ciao,
Johannes
next prev parent reply other threads:[~2018-03-22 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 22:15 [GSoC] Regarding "Convert scripts to builtins" Paul Sebastian Ungureanu
2018-03-19 23:11 ` Christian Couder
2018-03-19 23:41 ` Christian Couder
2018-03-21 12:32 ` Johannes Schindelin
2018-03-21 19:17 ` Wink Saville
2018-03-22 17:32 ` Johannes Schindelin [this message]
2018-03-22 17:50 ` Wink Saville
2018-03-23 9:48 ` 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=nycvar.QRO.7.76.6.1803221831120.77@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=ungureanupaulsebastian@gmail.com \
--cc=wink@saville.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).