Re: Re: [Simulavr-devel] Discussion: how to proceed with thedeveloment on GIT repo?

[Joerg Wunsch]

As address@hidden wrote:

> I should have written "and make a copy of Onno's git repo the
> official repository.".

That would be fine with me, as long as the old simulavr-0.1.2 codebase
is not completely discarded then.

In theory, savannah can handle two VCSes in parallel for a single
project, so we could keep the old simulavr-0.1 code at CVS, and only
migrate the simulavrxx code to SVN or git, but I think that has a huge
potential for confusion, including some danger of someone still
accidentally committing simulavrxx code into the (then abandoned) CVS
tree.  Therefore, if there is consensus to migrate the repository to a
more modern VCS, I'd like to see the old code migrated as well.

I'm willing to help with the migration, as I've already got some
experience for that (I once migrated AVRDUDE from CVS to SVN on
savannah).  However, as I've got no personal experience with git, I
wouldn't want to be the primary officer on duty if the decision is to
migrate to git.

> Clicking on "request for inclusion" brought up an "unknown signer"
> message.

savannah uses a SSL certificate signed by CAcert.org.  Go to

https://www.cacert.org/index.php?id=3

and enter CAcert's root certificates into your browser.

> Even with commit privileges, I probably wouldn't use them.
> I find it way too easy to make a mess.

Well, if you are developing on it, you should commit.  Anything else
doesn't make sense.  There's nobody else who is willing and able to do
the work on your behalf.  It's a VCS, so whatever happens, it can
always be rolled back when really needed.

-- 
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)