public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] What's the process on switching version control system for eCos?
Date: Mon, 21 Sep 2009 09:51:00 -0000	[thread overview]
Message-ID: <c09652430909210250i3fb94d22qa688838e4745254d@mail.gmail.com> (raw)

eCos is run in an open manner.

Is there someone who's in charge of the process of switching to
a new distributed version control system?

Are we just throwing stuff around currently?

I'd like to see a renewed patch process in place as part
of the new version control system switch.

I guess the maintainers will have to make a choice on
behalf of the community, so there won't actually be a vote as
such. Since eCos is run in an open manner, this major
change should take the community's input and not
be presented as a fait accomplis though.

-- 
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2009-09-21  9:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21  9:51 Øyvind Harboe [this message]
2009-09-21 11:26 ` Alex Schuilenburg
2009-09-22 14:34 ` Bart Veer
2009-09-22 14:40   ` Øyvind Harboe
2009-09-22 15:00     ` [ECOS] " Sergei Organov
2009-09-22 15:42       ` Alex Schuilenburg
2009-09-22 15:57         ` Sergei Organov
2009-09-25  0:28           ` Jonathan Larmour
2009-09-25  7:58             ` Sergei Organov
2009-09-22 16:09   ` [ECOS] " Alex Schuilenburg
2009-09-25  0:33     ` Jonathan Larmour
2009-10-01 11:43 ` [ECOS] Help required for LDI file Himanshu Patel
2009-10-01 21:14   ` [ECOS] " John Dallaway

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=c09652430909210250i3fb94d22qa688838e4745254d@mail.gmail.com \
    --to=oyvind.harboe@zylin.com \
    --cc=ecos-discuss@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).