public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@jifvik.org>
To: eCos Maintainers <ecos-maintainers@ecos.sourceware.org>
Subject: Re: Replacing CVS - time to vote
Date: Tue, 11 May 2010 16:00:00 -0000	[thread overview]
Message-ID: <4BE97F24.3030209@jifvik.org> (raw)
In-Reply-To: <4BE2F250.2090603@jifvik.org>

On 06/05/10 17:46, Jonathan Larmour wrote:
> 
> I'd like people to reply, even if the answer is "don't care". If not
> everyone has replied by next Thursday, then I'll announce the outcome
> regardless.

All but one maintainer has now replied, but there is now a majority
decision regardless: mercurial.

There were 2 votes for git and 5 votes for mercurial, along with one
explicit "don't care which". I didn't say that it was to be anonymous (I
didn't intend it to be) but because I didn't, I won't reveal who opted for
which unless people want me to. FWIW, I preferred mercurial.

To make it happen, I'll touch base with Alex Schuilenburg as it's clear he
has experience. In particular, to find out if sourceware's hg v1.2.1 is
good enough on the server side, or if it's worth upgrading (which will
require co-ordination with sourceware overseers). By rights it should be
ok, but main concern would be making sure the hg-git plugin will work ok,
so git users will be happy.

The actual switch should be relatively straightforward given, as mentioned
before, the existence of eCosCentric's converted repo which I'd just clone
wholesale. But before any roll-out we'll need to update web pages about
anoncvs. I should also put together a crib sheet and committing guidelines
for maintainers.

Jifl
-- 
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine

  parent reply	other threads:[~2010-05-11 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 16:46 Jonathan Larmour
2010-05-10 12:57 ` Sergei Gavrikov
2010-05-11 16:00 ` Jonathan Larmour [this message]
2010-05-11 19:39   ` Jonathan Larmour

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=4BE97F24.3030209@jifvik.org \
    --to=jifl@jifvik.org \
    --cc=ecos-maintainers@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).