git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Mike McLean <stixmclean@googlemail.com>
To: git@vger.kernel.org
Subject: Git Feature Request (Fixdown in interactive rebase)
Date: Wed, 23 Dec 2020 23:08:58 +0000	[thread overview]
Message-ID: <CAM0jFOdCD1uEcHaPB_go7aarapEBKx6M4d35zVOP8h9=MuZEmA@mail.gmail.com> (raw)
In-Reply-To: <CAM0jFOeCE-iTAMkiGE6m8bVNjJRn-BUmbUAP2ANrj4FbhuQG=g@mail.gmail.com>

I initially raised this as a FR with my git UI of choice, and was told
that it was actually something that git itself would need to do ...
and that the standard way to raise Feature Requests was to email this
list.

Apologies if that's not actually what I should be doing - please let
me know if this is not an intended use.

=-=-=-=-=-=-=-=

During an interactive rebase, the text file defining the operations
has a command option for "fixup".
This will squash the target commit into the previous commit (listed
above it in the file), and automatically use the commit message of the
previous commit (thus bypassing the "choose the commit message"
dialog/file).

Can we have a similar convenience-command that squashes, and retains
the second commit's message? Purpose is the same as the fixup command
- saving a bit of time and unnecessary typing during a common
operation.

Am happy to suggest names and/or shorthand keys for it, if the idea is
acceptable.

Yours,
Brondahl

       reply	other threads:[~2020-12-23 23:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAM0jFOeCE-iTAMkiGE6m8bVNjJRn-BUmbUAP2ANrj4FbhuQG=g@mail.gmail.com>
2020-12-23 23:08 ` Mike McLean [this message]
2020-12-23 23:25   ` Git Feature Request (Fixdown in interactive rebase) brian m. carlson
2020-12-23 23:28     ` Mike McLean
2020-12-23 23:57   ` Junio C Hamano
2020-12-24  0:13     ` Mike McLean
2020-12-24  9:16       ` Johannes Sixt
2020-12-24 22:21         ` Junio C Hamano
2020-12-24 22:54           ` Johannes Sixt
2021-01-06 22:40             ` Johannes Schindelin
2021-01-27  7:55   ` Charvi Mendiratta

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='CAM0jFOdCD1uEcHaPB_go7aarapEBKx6M4d35zVOP8h9=MuZEmA@mail.gmail.com' \
    --to=stixmclean@googlemail.com \
    --cc=git@vger.kernel.org \
    /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).