From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Bert Wesarg <bert.wesarg@googlemail.com>
Cc: git@vger.kernel.org
Subject: TopGit successor
Date: Mon, 8 Jun 2009 09:44:37 +0200 [thread overview]
Message-ID: <20090608074437.GA12109@pengutronix.de> (raw)
In-Reply-To: <36ca99e90906080031r3f5f545eo26c077e1966bf67@mail.gmail.com>
Hello Bert,
On Mon, Jun 08, 2009 at 09:31:01AM +0200, Bert Wesarg wrote:
> BTW: Do you have any infos or need help on your TopGit successor?
I want to get running at least the patch command, then I'm willing to
share it. The key difference to topgit is that it doesn't use branches
to track dependencies only commits. I hope this will make some things
easier and cleaner.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2009-06-08 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 20:41 [TopGit PATCH] hooks/pre-commit: check for cycles in dependencies Bert Wesarg
2009-06-04 21:33 ` Bert Wesarg
2009-06-05 20:25 ` Uwe Kleine-König
2009-06-08 7:31 ` Bert Wesarg
2009-06-08 7:44 ` Uwe Kleine-König [this message]
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=20090608074437.GA12109@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=bert.wesarg@googlemail.com \
--cc=git@vger.kernel.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).