From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.2 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI, STOX_REPLY_TYPE shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id 4510B1F424 for ; Sun, 22 Apr 2018 16:11:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753657AbeDVN4B (ORCPT ); Sun, 22 Apr 2018 09:56:01 -0400 Received: from smtp-out-1.talktalk.net ([62.24.135.65]:42638 "EHLO smtp-out-1.talktalk.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753619AbeDVNz5 (ORCPT ); Sun, 22 Apr 2018 09:55:57 -0400 Received: from PhilipOakley ([92.29.14.162]) by smtp.talktalk.net with SMTP id AFT3f1yXH4ZqzAFT3flNNt; Sun, 22 Apr 2018 14:55:56 +0100 X-Originating-IP: [92.29.14.162] X-Spam: 0 X-OAuthority: v=2.3 cv=E/fjW5Vl c=1 sm=1 tr=0 a=NXc+vVEgz70gitWznrz3ig==:117 a=NXc+vVEgz70gitWznrz3ig==:17 a=8nJEP1OIZ-IA:10 a=7OHT2rtye4MOl_pxVI4A:9 a=-rpqc9YgKvHJMETd:21 a=1qxa-s_SNQlgF5yC:21 a=wPNLvfGTeEIA:10 Message-ID: <57A18662264741D1A6CD3A10C8749175@PhilipOakley> Reply-To: "Philip Oakley" From: "Philip Oakley" To: "Johannes Schindelin" , Cc: "Junio C Hamano" , "Jacob Keller" , "Stefan Beller" , "Eric Sunshine" , "Phillip Wood" , "Igor Djordjevic" , "Johannes Sixt" , "Sergey Organov" , =?iso-8859-1?Q?Martin_=C5gren?= References: <7360a072f6fdd276d30839613434329b645e2cce.1524306546.git.johannes.schindelin@gmx.de> Subject: Re: [PATCH v8 06/16] sequencer: introduce the `merge` command Date: Sun, 22 Apr 2018 14:55:54 +0100 Organization: OPDS MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-Antivirus: AVG (VPS 180422-0, 22/04/2018), Outbound message X-Antivirus-Status: Clean X-CMAE-Envelope: MS4wfIbjmIouA0RD1XzFJG6nP7f3+QrNbSPjDFvo0odpzIRCGChWYr0wCIUm/5YxJ7AXCs1AbbN0ax81epNh4yWfICbts696tBSHz/f8+j9ykuZ09q5egTzJ a4M7rAzZkqCckpP3vFwtI33iANNgKcDJZZt6Fh97coadW/WoAAdj5mxEHr1/LiKYyzu3xEFbuz5ZXWo3XKPQhqHQ+PuhJnnQyizX57JGj08+rgecyrRh8MA7 N0UV2apsLVt545QFPIak/Rq6wkD9up7SS2hGuQRr7fJSJTSw9RUGrdFEXYGsTV3QKOVCpf6qQfkcS5yj4SF/0BmzLQRd9iIV2/hRYA3BN8YiczE/Y2XfVOHD 8ErnBDUj1lHzJC4CDLcLE9Ji8ypNxSlM+6AX8Hnv0eN7L8A8IsrixMxHY0Fn4Rev3oY3Nd7T8EN0ktDC8LaRU+4mAnoQH1R2xTxdpXfwjGkhZU5tDViE7fwo LUh4o78s+nFchqmSp7OEdo6s2JrBl7J0nrFyfQ== Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org From: "Johannes Schindelin" > This patch is part of the effort to reimplement `--preserve-merges` with > a substantially improved design, a design that has been developed in the > Git for Windows project to maintain the dozens of Windows-specific patch > series on top of upstream Git. > > The previous patch implemented the `label` and `reset` commands to label The previous patch was [Patch 05/16] git-rebase--interactive: clarify arguments, so this statement doesn't appear to be true. Has a patch been missed or re-ordered? Or should it be simply "This patch implements" ? Likewise the patch subject would be updated. > commits and to reset to labeled commits. This patch adds the `merge` s/adds/also adds/ ? > command, with the following syntax: > > merge [-C ] # > > The parameter in this instance is the *original* merge commit, > whose author and message will be used for the merge commit that is about > to be created. > > The parameter refers to the (possibly rewritten) revision to > merge. Let's see an example of a todo list: > The example ought to also note that `label onto` is to `# label current HEAD with a name`, seeing as this is the first occurance. It may be obvious in retrospect, but not at first reading. > label onto > > # Branch abc > reset onto Is this reset strictly necessary. We are already there @head. > pick deadbeef Hello, world! > label abc > > reset onto > pick cafecafe And now for something completely different > merge -C baaabaaa abc # Merge the branch 'abc' into master > > To edit the merge commit's message (a "reword" for merges, if you will), > use `-c` (lower-case) instead of `-C`; this convention was borrowed from > `git commit` that also supports `-c` and `-C` with similar meanings. > > To create *new* merges, i.e. without copying the commit message from an > existing commit, simply omit the `-C ` parameter (which will > open an editor for the merge message): > > merge abc > > This comes in handy when splitting a branch into two or more branches. > > Note: this patch only adds support for recursive merges, to keep things > simple. Support for octopus merges will be added later in a separate > patch series, support for merges using strategies other than the > recursive merge is left for the future. > > Signed-off-by: Johannes Schindelin > --- > git-rebase--interactive.sh | 6 + > sequencer.c | 407 ++++++++++++++++++++++++++++++++++++- > 2 files changed, 406 insertions(+), 7 deletions(-) > > diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh > index e1b865f43f2..ccd5254d1c9 100644 > --- a/git-rebase--interactive.sh > +++ b/git-rebase--interactive.sh > @@ -162,6 +162,12 @@ s, squash = use commit, but meld into > previous commit > f, fixup = like \"squash\", but discard this commit's log message > x, exec = run command (the rest of the line) using shell > d, drop = remove commit > +l, label