From: Michael Krelin <hacker@klever.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: monotone/git (was hello...)
Date: Thu, 04 Oct 2007 15:51:10 +0200 [thread overview]
Message-ID: <4704EFCE.6040407@klever.net> (raw)
In-Reply-To: <EB5E2840-5F10-45F9-8B97-9FCFDC7F5AAE@selfish.org>
> this will be my only to this topic but I see that as following:
Why won't you clarify your points?
> git:
> cons:
> - Incompats with other versions
What do you mean?
> - repacking (even if probably all known races are fixed)
That's not a contra if we compare with monotone.
> - shell mess with bashism and GNUism
Very true and, likely to be a show-stopper, anyway.
> - still complicated to use
Well, if you use the monotone subset of git, it's not ;-)
> - Does not track directories
Is it a problem with OE?
> mtn:
> cons:
> - Speed on rev pulling (I think mtn ls and status, diff is quite fast)
> - we can not easily merge the dreambox branch (this is why I wrote
> mtn2git)
Aha, now I know the script exists :-)
> pros:
> + trust (I don't feel like remembering the latest over night)
Can you elaborate on the expression in parentheses?
> + awesome manual
I wouldn't call it awesome when it goes beyond trivialities, but I don't
think it's a problem with either SCM.
> + trusting the code base (git is catching up, Linus is a god...
> but...)
Well, OE relies on git codebase indirectly anyway ;-)
> + certs attachable to revs
> + attributes and other testresults are attachable to files and it
> is on my todolist to use them
> + tracks directories
> + portable
>
>
> The last three/four reasons are the one why I would propose to stay
> with mtn as the main repository. I'm also working on a git2mtn script
> (after having merged the dreambox branch) which could make git a
> (semi) supported system for OE (if someone will host it).
The bottom line is - we're not going to move anytime soon. And I agree
it makes sense. I'm yet to see what are these attributes and other
testresults attachable to files (sounds interesting), but I'm a bit
afraid of your idea of (ab)using it, since that may make us get stuck
with mtn in the future no matter what.
Love,
H
next prev parent reply other threads:[~2007-10-04 13:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 10:41 hello Tobias Pflug
2007-10-04 11:18 ` hello Michael Krelin
2007-10-04 12:40 ` hello Holger Freyther
2007-10-04 12:55 ` monotone/git (was hello...) Tobias Pflug
2007-10-04 13:27 ` Holger Freyther
2007-10-04 13:50 ` Darcy Watkins
2007-10-04 13:52 ` Michael Krelin
2007-10-05 6:28 ` oe for two target boards at the same time Alex
2007-10-05 13:57 ` Cliff Brake
2007-10-05 15:47 ` Khem Raj
2007-10-06 8:19 ` Koen Kooi
2007-10-06 11:39 ` Marcin Juszkiewicz
2007-10-08 20:20 ` Cliff Brake
2007-10-09 8:28 ` Koen Kooi
2007-10-09 9:02 ` pHilipp Zabel
2007-10-09 10:36 ` Richard Purdie
2007-10-09 11:18 ` Graeme Gregory
2007-10-09 11:49 ` Graeme Gregory
2007-10-09 16:52 ` Paul Sokolovsky
2007-10-09 16:48 ` Paul Sokolovsky
2007-10-04 18:02 ` monotone/git (was hello...) Richard Purdie
2007-10-04 13:51 ` Michael Krelin [this message]
2007-10-04 13:30 ` Michael Krelin
2007-10-04 18:36 ` Chris Larson
2007-10-04 18:49 ` Tim Bird
2007-10-04 18:57 ` Chris Larson
2007-10-04 19:11 ` Michael Krelin
2007-10-04 19:27 ` Chris Larson
2007-10-04 19:39 ` Michael Krelin
2007-10-04 20:18 ` Chris Larson
2007-10-04 20:53 ` Michael Krelin
2007-10-04 19:08 ` Michael Krelin
2007-10-04 19:28 ` Chris Larson
2007-10-04 13:19 ` hello Michael Krelin
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=4704EFCE.6040407@klever.net \
--to=hacker@klever.net \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.