From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, mhagger@alum.mit.edu
Cc: git@vger.kernel.org
Subject: Re: Git feature request: --amend older commit
Date: 17 Aug 2012 13:00:05 -0400 [thread overview]
Message-ID: <20120817170005.27451.qmail@science.horizon.com> (raw)
In-Reply-To: <502E725B.2040906@alum.mit.edu>
> Have you tried "git rebase --autosquash"? It does part of what you are
> asking for and additionally allows multiple fixup commits to be queued
> up and processed in a single rebase.
No, I hadn't! It's not *quite* as simple as what I had hoped for, but
definitely is progress in that direction.
In particular, I can probably manage to use those to write a script that
does what I want. Something that ends up with something like
"EDITOR=/bin/true git rebase -i --autosquash $base"
Thanks you! I apologize for my failure to (Re-) RTFM. I have done so
numerous times, but the feature wasn't there last time I looked.
next prev parent reply other threads:[~2012-08-17 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 15:47 Git feature request: --amend older commit George Spelvin
2012-08-17 16:33 ` Michael Haggerty
2012-08-17 17:00 ` George Spelvin [this message]
2012-08-17 16:37 ` Thomas Rast
2012-08-18 1:41 ` Jared Hance
2012-08-18 21:57 ` Junio C Hamano
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=20120817170005.27451.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/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 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 NNTP newsgroup(s).