From: Sergey Organov <sorganov@gmail.com>
To: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
Cc: Christian Couder <christian.couder@gmail.com>,
git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>,
Jakub Narebski <jnareb@gmail.com>,
Markus Jansen <mja@jansen-preisler.de>,
Gabriel Alcaras <gabriel.alcaras@telecom-paristech.fr>,
Jeff King <peff@peff.net>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Jiang Xin <worldhello.net@gmail.com>,
Jacob Keller <jacob.keller@gmail.com>,
Eric Sunshine <sunshine@sunshineco.com>,
Igor Djordjevic <igor.d.djordjevic@gmail.com>,
Johannes Sixt <j6t@kdbg.org>,
Phillip Wood <phillip.wood@talktalk.net>,
Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: Draft of Git Rev News edition 38
Date: Mon, 16 Apr 2018 18:19:43 +0300 [thread overview]
Message-ID: <87efjf6uwg.fsf@javad.com> (raw)
In-Reply-To: <72f42205-c9c6-03aa-e8df-12e7062e8e62@gmail.com> (Kaartic Sivaraam's message of "Mon, 16 Apr 2018 20:37:16 +0530")
Kaartic Sivaraam <kaartic.sivaraam@gmail.com> writes:
> Hi,
>
> On Monday 16 April 2018 08:33 PM, Sergey Organov wrote:
>> Christian Couder <christian.couder@gmail.com> writes:
>>> Here "the above article" means the Jake's "branch -l: print useful
>>> info whilst rebasing a non-local branch" article above the current
>>> article.
>
> Just a little correction. I suppose Chris actually meant the "rebase -i:
> offer to recreate merge commits" article written by Jake and not the
> "branch -l: print useful info whilst rebasing a non-local branch" article.
>
> That said, I read the draft and found it good except for two minor issues,
>
> 1. I see the following sentence in the "Rebasing merges: a jorney to the
> ultimate solution (Road Clear) (written by Jacob Keller)" article
>
> "A few examples were tried, but it was proven that the original
> concept did not work, as dropped commits could end up being
> replaid into the merge commits, turning them into "evil"
> merges."
>
> I'm not sure if 'replaid' is proper English assuming the past tense of
> replay was intended there (which I think is 'replayed').
It could have meant, say, "reapplied", -- we need to ask the author.
While we are at it, please also consider to replace "original concept"
by "original algorithm", as it didn't work due to a mistake in the
algorithm as opposed to failure of the concept itself.
-- Sergey
next prev parent reply other threads:[~2018-04-16 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 22:11 Draft of Git Rev News edition 38 Christian Couder
2018-04-16 8:55 ` Christian Couder
2018-04-16 12:29 ` Sergey Organov
2018-04-16 13:08 ` Christian Couder
2018-04-16 15:03 ` Sergey Organov
2018-04-16 15:07 ` Kaartic Sivaraam
2018-04-16 15:19 ` Sergey Organov [this message]
2018-04-16 22:30 ` Christian Couder
2018-04-17 0:58 ` Jacob Keller
2018-04-16 22:26 ` Christian Couder
2018-04-17 2:17 ` Kaartic Sivaraam
2018-04-17 7:33 ` Christian Couder
2018-04-16 15:52 ` Jacob Keller
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=87efjf6uwg.fsf@javad.com \
--to=sorganov@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=christian.couder@gmail.com \
--cc=gabriel.alcaras@telecom-paristech.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=igor.d.djordjevic@gmail.com \
--cc=j6t@kdbg.org \
--cc=jacob.keller@gmail.com \
--cc=jnareb@gmail.com \
--cc=kaartic.sivaraam@gmail.com \
--cc=mja@jansen-preisler.de \
--cc=peff@peff.net \
--cc=phillip.wood@dunelm.org.uk \
--cc=phillip.wood@talktalk.net \
--cc=sunshine@sunshineco.com \
--cc=worldhello.net@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.