From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Petr Baudis" <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] TopGit - A different patch queue manager
Date: Sun, 3 Aug 2008 10:45:06 -0400 [thread overview]
Message-ID: <9e4733910808030745j275eaffdib8a412fa95911bb3@mail.gmail.com> (raw)
In-Reply-To: <20080803031424.GV32184@machine.or.cz>
On 8/2/08, Petr Baudis <pasky@suse.cz> wrote:
> TopGit is meant as a fresh start in the steps of StGIT, quilt-in-git
> and others, of course in an attempt to Get It Right this time around.
> TopGit is absolutely minimal porcelain layer that will manage your
> patch queue for you using topic branches, one patch per branch.
> And do _ONLY_ that. Unlike with StGIT, you can actually use the index.
It is very helpful to block git commands that will mess up the state
of topgit. For example 'git rebase' is a good way to mess up stgit.
Instead you need to do 'stg rebase'. It is quite easy to type the
wrong command when switching between trees and some are under stgit
and others aren't.
I believe there is a stgit rewrite due any day now that completely
changes how it deals with the index.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-08-03 14:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-03 3:14 [ANNOUNCE] TopGit - A different patch queue manager Petr Baudis
2008-08-03 7:27 ` Miklos Vajna
2008-08-03 12:02 ` Petr Baudis
2008-08-03 14:14 ` [PATCH] [TopGit] Check for pre-commit hook existence Russell Steicke
2008-08-03 14:26 ` Petr Baudis
2008-08-03 14:45 ` Jon Smirl [this message]
2008-08-04 13:22 ` [ANNOUNCE] TopGit - A different patch queue manager Karl Hasselström
2008-08-07 17:56 ` linearising TopGit forests into patch series (was: [ANNOUNCE] TopGit - A different patch queue manager) martin f krafft
2008-08-07 19:58 ` Bert Wesarg
2008-08-08 17:06 ` martin f krafft
2008-08-08 17:14 ` Bert Wesarg
2008-08-09 1:08 ` Petr Baudis
2008-08-10 20:54 ` Petr Baudis
2008-08-09 2:09 ` Sam Vilain
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=9e4733910808030745j275eaffdib8a412fa95911bb3@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--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).