From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Jakub Narebski <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: Some ideas for StGIT
Date: Sun, 5 Aug 2007 14:56:23 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0708051452280.14781@racer.site> (raw)
In-Reply-To: <20070805133940.GA18835@filer.fsl.cs.sunysb.edu>
Hi,
On Sun, 5 Aug 2007, Josef Sipek wrote:
> On Sat, Aug 04, 2007 at 10:31:30PM -0400, Shawn O. Pearce wrote:
> ...
> [rebase is complex but fun]
>
> Great, but does git have something that could replace
> $QUILT_LIKE_APP refresh?
What does "refresh"? (I never used quilt, and probably never will, since
rebase -i does what I need.)
> Sure, if you can take 2 commits and collapse them into one you could
> fake it by creating a dummy commit with the new changes, and then
> collapsing, but that's nasty - and reflog might not like that much :)
IIUC you want to edit/amend a patch in the middle of a series? Two ways
to go about it:
1) (preferred)
* start rebase -i
* mark the commit as "edit"
* wait until rebase stops to let you edit it
* edit, test, commit --amend
* rebase --continue
2) (not so preferred, but often convenient)
* fix bug
* commit with a dummy message
* rebase -i
* move commit just after the commit-to-edit
* mark second as "squash"
* when the editor comes up, just delete the second
commit's message, and possibly adjust the first's
Hth,
Dscho
next prev parent reply other threads:[~2007-08-05 13:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 17:50 Some ideas for StGIT Pavel Roskin
2007-08-03 18:14 ` Andy Parkins
2007-08-04 5:41 ` Pavel Roskin
2007-08-04 5:51 ` Shawn O. Pearce
2007-08-05 0:08 ` Pavel Roskin
2007-08-05 0:17 ` Jakub Narebski
2007-08-05 2:31 ` Shawn O. Pearce
2007-08-05 3:32 ` Junio C Hamano
2007-08-05 13:39 ` Josef Sipek
2007-08-05 13:56 ` Johannes Schindelin [this message]
2007-08-05 14:06 ` Josef Sipek
2007-08-05 14:15 ` Johannes Schindelin
2007-08-05 14:57 ` Josef Sipek
2007-08-04 8:08 ` Yann Dirson
2007-08-06 10:01 ` Catalin Marinas
2007-08-04 14:14 ` Chris Shoemaker
2007-08-04 15:22 ` Johannes Schindelin
2007-08-03 23:23 ` Yann Dirson
2007-08-06 9:49 ` Catalin Marinas
2007-08-06 13:26 ` Pavel Roskin
2007-08-06 15:19 ` Josef Sipek
2007-08-04 6:38 ` Theodore Tso
2007-08-04 8:16 ` Yann Dirson
2007-08-04 21:35 ` Josef Sipek
2007-08-05 0:12 ` Pavel Roskin
2007-08-06 9:36 ` Catalin Marinas
2007-08-06 9:56 ` Karl Hasselström
2007-08-06 12:42 ` Pavel Roskin
2007-08-06 13:52 ` Karl Hasselström
2007-08-23 14:09 ` Catalin Marinas
2007-08-23 14:34 ` Karl Hasselström
2007-08-06 17:17 ` Pavel Roskin
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=Pine.LNX.4.64.0708051452280.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=jsipek@fsl.cs.sunysb.edu \
--cc=spearce@spearce.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.
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).