git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* porcelain question: state of the art for undo-redo?
@ 2005-06-11  8:51 Jon Seymour
  2005-06-14  1:25 ` Daniel Barkalow
  0 siblings, 1 reply; 2+ messages in thread
From: Jon Seymour @ 2005-06-11  8:51 UTC (permalink / raw)
  To: Git Mailing List

What porcelain layer solutions currently exist for effective undo-edit-redo?

For example, if you are working on a series of patches in a series,
then realise there is a mistake in a patch early in the series, how
does one mod that patch, then reapply all the following patches to
produce a slightly modified patch series with as little stuffing
around as possible?

jon.
-- 
homepage: http://www.zeta.org.au/~jon/
blog: http://orwelliantremors.blogspot.com/

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: porcelain question: state of the art for undo-redo?
  2005-06-11  8:51 porcelain question: state of the art for undo-redo? Jon Seymour
@ 2005-06-14  1:25 ` Daniel Barkalow
  0 siblings, 0 replies; 2+ messages in thread
From: Daniel Barkalow @ 2005-06-14  1:25 UTC (permalink / raw)
  To: jon; +Cc: Git Mailing List

On Sat, 11 Jun 2005, Jon Seymour wrote:

> What porcelain layer solutions currently exist for effective undo-edit-redo?
> 
> For example, if you are working on a series of patches in a series,
> then realise there is a mistake in a patch early in the series, how
> does one mod that patch, then reapply all the following patches to
> produce a slightly modified patch series with as little stuffing
> around as possible?

I personally commit changes as I make them (essentially, and time I'm
about to make a change that might not work out, I commit the previous
state). Once I'm completely satisfied with the results, I redo the whole
thing as a series of commits from the base as self-contained changes.

To do this, I get a repository which contains the base (as master) and the
result of my previous work. Then I repeat the following steps:

Diff the work against the head into a temporary file.
Remove all of the hunks I don't want yet from the file.
Apply the file.
Commit.

I stop when the diff is either empty or contains only junk I didn't
actually mean to include.

Then I submit the series thus created.

I generally then diff once more, remove anything I actually don't want to
have (as opposed to wanting to have but not submit), apply and commit to
form a new work head. Then I throw away the old work head.

If I screw this up, I just start over, since I have all the actual content
safe.

	-Daniel
*This .sig left intentionally blank*


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-06-14  1:22 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-06-11  8:51 porcelain question: state of the art for undo-redo? Jon Seymour
2005-06-14  1:25 ` Daniel Barkalow

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).