[En-Nut-Discussion] Change Ethernut repository to SVN
Thiago A. Corrêa
thiago.correa at gmail.com
Thu Aug 28 19:53:32 CEST 2008
On Thu, Aug 28, 2008 at 1:06 PM, Harald Kipp <harald.kipp at egnite.de> 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.
Thiago A. Correa
More information about the En-Nut-Discussion