From: Nanako Shiraishi <nanako3@lavabit.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: Bjrn Steinbrink <B.Steinbrink@gmx.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: rebase-with-history -- a technique for rebasing without trashing your repo history
Date: Sat, 15 Aug 2009 06:40:01 +0900 [thread overview]
Message-ID: <20090815064001.6117@nanako3.lavabit.com> (raw)
In-Reply-To: <4A85D53D.9050805@alum.mit.edu>
Quoting Michael Haggerty <mhagger@alum.mit.edu>
> In [1] I compared rebase-with-history with both of the
> currently-available options (rebase and merge). Rebase and merge can
> each deal with some of the issues that come up, but each one falls flat
> on others. I believe that rebase-with-history has the advantages of both.
> .... Rebase-with-history is obviously
> not an earth-shattering revolution in DVCS technology, but my hope is
> that it could unobtrusively assist with a few minor pain points.
The saddest part is that your [1] works only in a case a user can easily handle manually, and doesn't help cases more complex than the most trivial ones, such as reordering and squashing commits, where the user may benefit if an automated support from VCS were available.
--
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
next prev parent reply other threads:[~2009-08-14 21:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 12:46 rebase-with-history -- a technique for rebasing without trashing your repo history Michael Haggerty
2009-08-13 16:12 ` Björn Steinbrink
2009-08-13 22:39 ` Michael Haggerty
2009-08-13 23:30 ` Björn Steinbrink
2009-08-14 21:21 ` Michael Haggerty
2009-08-14 21:40 ` Nanako Shiraishi [this message]
2009-08-15 3:36 ` Björn Steinbrink
2009-08-14 3:17 ` Sitaram Chamarty
2009-08-13 17:39 ` Bryan O'Sullivan
2009-08-13 20:31 ` Abderrahim Kitouni
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=20090815064001.6117@nanako3.lavabit.com \
--to=nanako3@lavabit.com \
--cc=B.Steinbrink@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.