From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Nigel Stephens <nigel@mips.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: Git
Date: Wed, 14 Sep 2005 17:44:53 +0200 [thread overview]
Message-ID: <20050914154453.GL23161@lug-owl.de> (raw)
In-Reply-To: <43284153.1040508@mips.com>
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
Ni Nigel!
On Wed, 2005-09-14 16:27:15 +0100, Nigel Stephens <nigel@mips.com> wrote:
> 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.
No, not yet, mostly due to time reasons. But I second it sounds
useful.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-14 15:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 12:45 Git Ralf Baechle
2005-09-13 12:15 ` Git sjhill
2005-09-13 13:21 ` Git Ralf Baechle
2005-09-13 13:34 ` Git Jan-Benedict Glaw
2005-09-13 14:50 ` Git Thiemo Seufer
2005-09-13 13:31 ` Git Jan-Benedict Glaw
2005-09-13 15:20 ` Git Ralf Baechle
2005-09-14 9:45 ` Git Dominic Sweetman
2005-09-14 12:55 ` [PATCH] Ethernet for TX4927(37) platform Vladimir A. Barinov
2005-09-14 13:02 ` [PATCH] RTC " Vladimir A. Barinov
2005-09-14 13:04 ` [PATCH] Remove compile warnings " Vladimir A. Barinov
2005-09-14 13:08 ` [PATCH] Fix module insertion fail for TX4927/TX4938 platforms Vladimir A. Barinov
2005-09-14 15:17 ` [PATCH] Ethernet for TX4927(37) platform Jan-Benedict Glaw
2005-09-14 9:58 ` Git Jan-Benedict Glaw
2005-09-14 11:23 ` Git Geert Uytterhoeven
2005-09-14 11:46 ` Git Jan-Benedict Glaw
2005-09-14 12:37 ` Git Ralf Baechle
2005-09-14 13:01 ` Git Thiemo Seufer
2005-09-14 15:21 ` Git Jan-Benedict Glaw
2005-09-14 15:27 ` Git Nigel Stephens
2005-09-14 15:44 ` Jan-Benedict Glaw [this message]
2005-09-13 18:43 ` Git Wolfgang Denk
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=20050914154453.GL23161@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-mips@linux-mips.org \
--cc=nigel@mips.com \
--cc=ralf@linux-mips.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