From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Re: Summary of an unwanted merge and what I did
Date: Tue, 29 Apr 2008 08:06:20 -0400 [thread overview]
Message-ID: <48170F3C.7040409@balister.org> (raw)
In-Reply-To: <fv7289$ovv$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
There are lots of good feature and bad features to all the choices. What
it boils down to is many people want to use git because everyone else
does (I fall into the category), but git is a pain in the hind-quarters
to learn (I also fall into this category, ask me about git revert
sometime). Hg is the closest replacement for monotone, but it suffers
from a small (but expanding) user base. Then there are "technical"
reasons that I'll skip :)
Then there is the school of thought that we should just make everyone
unhappy and use Visual Source Safe or ClearCase.
Philip
Rolf Leggewie wrote:
> Thanks, Richard, for the update.
>
> Richard Purdie wrote:
>> The 'core' team discussed it and didn't reach a consensus.
>
> You mean a unanimous vote? Or was there really wide disagreement?
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2008-04-29 12:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 11:44 Summary of an unwanted merge and what I did Holger Freyther
2008-04-28 14:39 ` Holger Freyther
2008-04-28 23:43 ` Rolf Leggewie
2008-04-29 0:33 ` Khem Raj
2008-04-29 8:19 ` Richard Purdie
2008-04-29 11:53 ` Rolf Leggewie
2008-04-29 12:06 ` Philip Balister [this message]
2008-04-29 13:43 ` Leon Woestenberg
2008-04-29 13:54 ` Michael 'Mickey' Lauer
2008-05-01 22:26 ` Justin Patrin
2008-05-01 22:33 ` Tim Bird
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=48170F3C.7040409@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.