From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: Git
Date: Wed, 14 Sep 2005 13:46:50 +0200 [thread overview]
Message-ID: <20050914114650.GF23161@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0509141322540.1923@numbat.sonytel.be>
[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]
On Wed, 2005-09-14 13:23:22 +0200, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Wed, 14 Sep 2005, Jan-Benedict Glaw wrote:
> > On Tue, 2005-09-13 16:20:38 +0100, Ralf Baechle <ralf@linux-mips.org> wrote:
> > > On Tue, Sep 13, 2005 at 03:31:26PM +0200, Jan-Benedict Glaw wrote:
> > > > I'm also on the way
> > > > getting familiar with GIT, doing my very first steps. It would be nice
> > > > if we'd present what we know in Oldenburg (I already offered to do so,
> > > > Joey planed it for Saturday).
> > >
> > > Sounds like a plan. And maybe present some of the other alternatives
> > > to CVS as well?
> >
> > I'm not sure if it's worth it. Linus decided against all other SCMs. I
> > did use (for small test projects) monotone, darcs and arch. (I think
> > all other alternatives aren't.)
>
> Have you tried mercurial?
Nope. I've only used it's web frontend on http://www.kernel.org/hg/ .
Mercurial's author claims that it scales even better than git, esp. on
its network transfer. However, I'm not aware how it scales there right
now, since git got its "packs" implemented.
> > 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.
>
> Still using plain patches and email...
...which is a nice and actually working scheme, too. At least, it
doesn't require to learn working with a new SCM :-P Though I think
it's a good idea.
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 11:47 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 ` Jan-Benedict Glaw [this message]
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 ` Git Jan-Benedict Glaw
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=20050914114650.GF23161@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=geert@linux-m68k.org \
--cc=linux-mips@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