From: Jan Nieuwenhuizen <janneke-list@xs4all.nl>
To: martin f krafft <madduck@madduck.net>
Cc: Petr Baudis <pasky@suse.cz>, git@vger.kernel.org
Subject: Re: [ANNOUNCE] TopGit v0.3
Date: Wed, 17 Sep 2008 12:48:40 +0200 [thread overview]
Message-ID: <1221648520.30402.12.camel@heerbeest> (raw)
In-Reply-To: <20080912181442.GA5407@lapse.rw.madduck.net>
On vr, 2008-09-12 at 19:14 +0100, martin f krafft wrote:
> I've considered this question a lot before and could not come up
> with anything; you cannot undo a merge.
Isn't that overly pessimistic? Can't we have git create a merge
commit that can be reverted with git revert?
For our ooo-build use case, I'm hoping to use [top]git as "a better
patch" and hope to have mostly orthogonal topic branches. With patch,
to "undo a merge" usually means patch -R and remove the patch from
the dependency list. I can hardly imagine something easily possible
with patch is still impossible with git.
Greetings,
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
next prev parent reply other threads:[~2008-09-17 10:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 23:10 [ANNOUNCE] TopGit v0.3 Petr Baudis
2008-09-10 8:18 ` Bert Wesarg
2008-09-12 11:01 ` Petr Baudis
2008-09-11 8:03 ` Jan Nieuwenhuizen
2008-09-12 11:00 ` Petr Baudis
2008-09-12 12:27 ` Jan Nieuwenhuizen
2008-09-12 13:15 ` Petr Baudis
2008-09-12 18:14 ` martin f krafft
2008-09-17 10:48 ` Jan Nieuwenhuizen [this message]
2008-09-21 14:24 ` Petr Baudis
2008-09-22 9:13 ` Jan Nieuwenhuizen
2008-09-22 15:27 ` Petr Baudis
2008-09-23 13:13 ` Jan Nieuwenhuizen
2008-09-23 13:27 ` Petr Baudis
2008-09-29 10:53 ` Jan Nieuwenhuizen
2008-10-03 10:00 ` Jan Holesovsky
[not found] ` <20080911054030.GA6602@glandium.org>
2008-09-12 10:58 ` Petr Baudis
2008-09-15 8:01 ` Michael Radziej
2008-09-17 10:11 ` Petr Baudis
2008-09-17 11:17 ` Michael Radziej
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=1221648520.30402.12.camel@heerbeest \
--to=janneke-list@xs4all.nl \
--cc=git@vger.kernel.org \
--cc=madduck@madduck.net \
--cc=pasky@suse.cz \
/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).