Commits on svn trunk ocl/rtt limited
| Submitted by sspr on Thu, 2009-06-04 15:15 |
In the light of RTT/OCL 2.0, I'm asking all people having commit access
to the subversion repositories to no longer commit on trunk/rtt and trunk/ocl
but send the patches on the ML. They will then first end up in my git
repository and are then sent towards the svn repository. Commits
on svn greatly makes merge tracking more difficult (technically: a rebase
of the git branch is done each time we sync with svn), if we want the git
repository to be the primary one.
That said, it would be even easier if no-one used these svn branches
anymore and everyone uses git. Mac/Linux are fine, Windows users need
to install a minimal cygwin set including git. Anyone can use the 'download'
link for getting a tar or zip archive on the github page:
http://github.com/psoetens/orocos-rtt/tree/master
For clarity, RTT/OCL 2.0 will not be made available on svn by my doing...
Peter
Commits on svn trunk ocl/rtt limited
On Thursday 04 June 2009 17:12:15 Peter Soetens wrote:
> In the light of RTT/OCL 2.0, I'm asking all people having commit access
> to the subversion repositories to no longer commit on trunk/rtt and
> trunk/ocl but send the patches on the ML. They will then first end up in my
> git repository and are then sent towards the svn repository. Commits
> on svn greatly makes merge tracking more difficult (technically: a rebase
> of the git branch is done each time we sync with svn), if we want the git
> repository to be the primary one.
>
> That said, it would be even easier if no-one used these svn branches
> anymore and everyone uses git. Mac/Linux are fine, Windows users need
> to install a minimal cygwin set including git.
AFAIK, the preferred way to have git on windows is to use msysgit, which is
standalone. Moreover, there is a tortoisegit available on google code.
Sylvain