[Tinyos-devel] tip of the cvs tree
Razvan Musaloiu-E.
razvanm at cs.jhu.edu
Thu Jun 19 02:11:32 PDT 2008
Hi!
On Wed, 18 Jun 2008, Philip Levis wrote:
>
> On Jun 18, 2008, at 9:24 PM, Razvan Musaloiu-E. wrote:
>
>> One thing we could try is to start using git with a main tree maintain by
>> Phil which he can publish to CVS the stable versions. I think this is
>> possible because there is already some structure in the way development is
>> done: David Moss is responsible with CC2420, Kevin Klues is responsible for
>> tosthreads, John Regehr is responsible for safe tinyos and so on.
>
> I guess my feeling is that this is contained and infrequent enough that CVS
> branches or even development areas are sufficient.
I haven't tried CVS branches but in svn I frequently had problems bringing
a branch up to date with respect with another one. What happened is I end
up with cases in which svn didn't properly delete the files that were
removed so I had to do a lot of grepping and svn rm/add to take care of
it.
> Git is really powerful, but it is also harder to use in the common case
> (git add, git commit, git push).
I'm not sure I understand why is this harder. One thing I forgot to
mention that I really like is the fact that merging will preserve the
original commit log so you can really see how something happen.
> Not to mention that the unit of commit, like svn, really doesn't match
> how heavily compartmentalized CVS is. It's very rare to have commits
> that touch many directories which you want to view as an atomic action.
After using svn and git I find awkward the per-file way of working of cvs.
It's really much easier to think in terms of revision number of a tree. It
is true that about half of the commits (49% or 530 out of 1068) are one
file but most of the changes (92% or 6520 out of 7050) are part of commits
that touched more than one file. The percentage is still high even for
changes that touch more than 5 files (77% or 6080 out of 7050).
--
Razvan ME
More information about the Tinyos-devel
mailing list