linux-mips
[Top] [All Lists]

Re: Git

To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Subject: Re: Git
From: Nigel Stephens <nigel@mips.com>
Date: Wed, 14 Sep 2005 16:27:15 +0100
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
In-reply-to: <20050914152144.GJ23161@lug-owl.de>
Organization: MIPS Technologies
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <20050913124544.GC3224@linux-mips.org> <20050913133126.GO23161@lug-owl.de> <20050913152038.GE3224@linux-mips.org> <20050914095858.GD23161@lug-owl.de> <20050914123750.GL3224@linux-mips.org> <20050914152144.GJ23161@lug-owl.de>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Debian Thunderbird 1.0.2 (X11/20050817)


Jan-Benedict Glaw wrote:

To get fixes/port updates/subsystem updates upstream to Linus, GIT is
the way[tm] to go, so we'd try to get familiar with it.
The other accepted currency of the trade are still simple patches, see
http://www.linux-mips.org/wiki/The_perfect_patch.

ACK. But unless you've got the perfect Patch Queue Manager that'll
re-diff and re-send your patches automatically to Linus, you keep on
doing some manual work or at least starting your scripts ever and ever
again :)


Speaking of patch management, has anyone tried out Stacked GIT (aka StGIT, aka quilt on GIT) at http://www.procode.org/stgit/? It looks like it could be useful, and can be used in conjunction with other porcelain like Cogito.

Nigel

<Prev in Thread] Current Thread [Next in Thread>