Change Ethernut repository to SVN

[Thiago A. Corrêa]

Hi,

    Since sourceforge supports SVN for quite sometime now, how about
moving the CVS repository to SVN? There is a tool that carries the
history from CVS to SVN, so we don't have to loose it.

    This would "fix" the problem Ole was talking about earlier with
the Changelog file as svn log works in a much better way than cvs log.
And we could have commit diffs easily posted automatically on the list
for review.

    Just a thought.

Kinds regards,
    Thiago A. Correa
_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Harald Kipp]

I have added the btnut list, because they'd be involved too.

Thiago A. Corrêa wrote:
>
>     Since sourceforge supports SVN for quite sometime now, how about
> moving the CVS repository to SVN? There is a tool that carries the
> history from CVS to SVN, so we don't have to loose it.

AFAIK the CVS history doesn't differ much from the one provided by SVN.

The ChangeLog is a kind of NEWS file with more general infos. Users may
get a rough overview here without going into the details of the file logs.


> And we could have commit diffs easily posted automatically on the list
> for review.

This is possible with CVS as well, it's simply not configured. However,
I'd prefer to have a distinct list (en-nut-commit) for this. Most
subscribers of nut-discussion won't be interested in such posts.

Anyway, it is planned to move to Subversion. As you may have noticed, I
no longer use $Log$ in newer files, because SVN won't support it.

The reason for not moving to Subversion so far is, that there are tons
of other items on my list. However, if someone wants to take over this
task, I'll support this.

We may also discuss first, if we should stay with SourceForge. The
problem is, that SourceForge doesn't allow to download the full
repository including all control files.

Harald





_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Thiago A. Corrêa]

On Thu, Aug 28, 2008 at 1:06 PM, Harald Kipp <harald.kipp@...> wrote:

> I have added the btnut list, because they'd be involved too.
>
> Thiago A. Corrêa wrote:
>>
>>     Since sourceforge supports SVN for quite sometime now, how about
>> moving the CVS repository to SVN? There is a tool that carries the
>> history from CVS to SVN, so we don't have to loose it.
>
> AFAIK the CVS history doesn't differ much from the one provided by SVN.
>
> The ChangeLog is a kind of NEWS file with more general infos. Users may
> get a rough overview here without going into the details of the file logs.
>

Actually, since svn commits are "atomic", a set of changed files all
share the same revision number and thru svn log one can figure out
which files chnaged in each checkin. This makes specifying the files
changed in the Changelog a bit less important.

Also, makes it quite easier to do branch and merge operations.

>> And we could have commit diffs easily posted automatically on the list
>> for review.
>
> This is possible with CVS as well, it's simply not configured. However,
> I'd prefer to have a distinct list (en-nut-commit) for this. Most
> subscribers of nut-discussion won't be interested in such posts.

That should work as well. It's quite low volume anyway.

>
> Anyway, it is planned to move to Subversion. As you may have noticed, I
> no longer use $Log$ in newer files, because SVN won't support it.
>
> The reason for not moving to Subversion so far is, that there are tons
> of other items on my list. However, if someone wants to take over this
> task, I'll support this.
>
> We may also discuss first, if we should stay with SourceForge. The
> problem is, that SourceForge doesn't allow to download the full
> repository including all control files.
>

I had a project (wpdev) at sourceforge that I moved from CVS to SVN. I
remember there was a documentation on the site about how to download
the full repository. There were steps that only the project admin
would be able to do in CVSROOT folder or something from the SF shell
server.  Later we moved on to berlios, but it was just because of
bandwidth issues at that time.

Att.
   Thiago A. Correa
_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Harald Kipp]

Thiago,

Thiago A. Corrêa wrote:
>
> Actually, since svn commits are "atomic", a set of changed files all
> share the same revision number and thru svn log one can figure out
> which files chnaged in each checkin. This makes specifying the files
> changed in the Changelog a bit less important.

Agreed.

> Also, makes it quite easier to do branch and merge operations.

Dito.

> server.  Later we moved on to berlios, but it was just because of
> bandwidth issues at that time.

Sourceforge's bandwidth, performance and refresh periods are quite well
these days. We only have to accept, that Sourceforge is not willing to
let us move the complete project history to another service.

IMHO, the recent commercialization of the site (banner ads etc.) is not
really annoying. But it is out of our control and may change when
financial pressure increases.

Harald



_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Ole Reinhardt-2]

Hi Harald,

> IMHO, the recent commercialization of the site (banner ads etc.) is not
> really annoying. But it is out of our control and may change when
> financial pressure increases.

Have you ever thought about hosting the project yourself? There are
several good packages like gforge to setup an own hosting site on your
server?

Regards,

Ole Reinhardt

--
 _____________________________________________________________
|                                                             |
| Embedded-IT          Hard- und Softwarelösungen             |
|                                                             |
| Ole Reinhardt        Tel. / Fax:        [phone] |
| Luisenstraße 29      Mobil:             [phone] |
| 57076 Siegen         eMail:    ole.reinhardt@... |
| Germany              Web:         http://www.embedded-it.de |
|                      UstID / VAT:       DE198944716         |
|_____________________________________________________________|

_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Thiago A. Corrêa]

Harald,

>> server.  Later we moved on to berlios, but it was just because of
>> bandwidth issues at that time.
>
> Sourceforge's bandwidth, performance and refresh periods are quite well
> these days. We only have to accept, that Sourceforge is not willing to
> let us move the complete project history to another service.

I just checked my old project (which still exists in it's outdated
form in SF), and it seams that they no longer provide tarballs but
they do allow us to download it via rsync.

http://alexandria.wiki.sourceforge.net/Subversion+-+Version+Control+for+Source+Code#tocSubversion%20-%20Version%20Control%20for%20Source%20Code5

Following their how to move from CVS to Subversion I was able to
create an svn dump of ethernut repository ready for being imported, so
it should be possible to move the complete history. cvs2svn even got
smarter than when I used, it seams to try to figure out the actual
changesets to perform a single commit into the target svn dump.

So, I guess we would just have to determine a commit window so others
have a chance to commit their work, then "freeze" for a day or so and
import things into svn.  We might even get it a test drive since it
seams to be easy to import back different dumps overwriting the
entiere repository. :-)

>
> IMHO, the recent commercialization of the site (banner ads etc.) is not
> really annoying. But it is out of our control and may change when
> financial pressure increases.
>

Yeah... I usually use Firefox's Adblock to filter out everything with wildcards.

Kind regards,
    Thiago A. Correa
_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion

[Matthias Ringwald]

Hi Harald

> I have added the btnut list, because they'd be involved too.

We're not to active lately, and I personally should finish this year  
anyway.
Nevertheless, I'm fine with a switch to SVN. My favorite argument for  
SVN is the "svn status" command which gives you an overview on your  
pending changes in a clear and concics manner, this is something CVS  
fails completely (or I am too stupid to read the man page - using grep  
or Version Control GUIs does not count). If you can just notify us a  
bit ahead of time that would be perfect. I don't think our  
cruisecontrol system will have trouble getting the nut/os sources from  
SVN instead of CVS.

regards,
  Matthias
_______________________________________________
http://lists.egnite.de/mailman/listinfo/en-nut-discussion