From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org, "martin f. krafft" <madduck@debian.org>
Subject: Re: topgit patches
Date: Thu, 26 Feb 2009 14:47:05 +0100 [thread overview]
Message-ID: <20090226134705.GB7110@pengutronix.de> (raw)
In-Reply-To: <20090225232237.GO12275@machine.or.cz>
Hi Petr,
On Thu, Feb 26, 2009 at 12:22:37AM +0100, Petr Baudis wrote:
> > If you give me push access I'd only push the first three patches to
> > master and maybe create a pu branch for the linearize method.
>
> I wouldn't be so conservative, IMHO it's better to liberally test new
> features rather than let them bitrot, in such a small project, but of
> course it's up to you.
OK, that's fine for me, too. This way it might at least get a few more
users. :)
> What's your repo.or.cz username?
ukleinek
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2009-02-26 13:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 19:58 topgit patches Uwe Kleine-König
2009-02-25 20:03 ` [PATCH] [TOPGIT] limit rev-list in branch_contains to a single rev Uwe Kleine-König
2009-02-25 20:03 ` [PATCH] [TOPGIT] allow working with annihilated branches Uwe Kleine-König
2009-02-25 20:03 ` [PATCH] [TOPGIT] make tg remote idempotent Uwe Kleine-König
2009-02-25 20:03 ` [PATCH] [TOPGIT] make creating a commit from a topgit branch a function Uwe Kleine-König
2009-02-25 20:04 ` [PATCH] [TOPGIT] implement linearize export method Uwe Kleine-König
2009-02-25 21:23 ` topgit patches Petr Baudis
2009-02-25 23:15 ` Uwe Kleine-König
2009-02-25 23:22 ` Petr Baudis
2009-02-26 13:47 ` Uwe Kleine-König [this message]
2009-02-26 6:06 ` martin f krafft
2009-02-26 14:15 ` Uwe Kleine-König
2009-02-27 12:37 ` martin f krafft
2009-02-27 19:42 ` Uwe Kleine-König
2009-03-02 16:26 ` Uwe Kleine-König
2009-03-03 7:54 ` martin f krafft
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=20090226134705.GB7110@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=git@vger.kernel.org \
--cc=madduck@debian.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).