Hello,

As you probably know Eric and I have been experimenting with git for the last 
month.  In fact, we have been committing to the SVN from a git repository.

One of the weaker points of git (totally understandable) is that the git-svn 
feature is not really very solid.  This is probably because few git users 
want to interface to SVN repositories, and they quickly convert to full git 
repositories.

Unfortunately, for some unknown reason, we are no longer able to commit to the 
SVN from git.  We had planned to switch over to using git in a few weeks, but 
this problem has accelerated the change at a rather inconvenient time (we are 
not ready for a smooth transfer).  So the transfer is going to be less smooth 
than we had hoped.

I have now removed the Bacula SVN projects named bacula, regress, and gui.  
The rescue and docs SVN projects still remain, for reasons I'll explain 
later.  So if any developer wants to commit to the bacula, regress, or gui 
code, it must now be committed into a different repository using git.

In our current plans (may evolve as needed), the git repository that we have 
created on Source Forge will remain as the master repository for checkouts of 
the source code.  This will be the most stable repository, and will get 
upgraded only when a patch or commit has been reviewed by a senior 
programmer.

A developer's git repository has been created on github, and this is where, in 
the beginning, developers will make their commits.  It exists, but we still 
need to document its usage, so it will be sometime next week when we can hook 
developers upto a git repository for making commits (actually pushes).  If 
you are a developer and want to commit, please let me know.

Anyone who wants a copy of the current development code in the most stable 
form, should create a clone of the Source Forge repository.  You can do that 
with:

git clone git://bacula.git.sourceforge.net/gitroot/bacula xxx

where xxx is the directory you want to be created.  Once it is done, you will 
find that directory contains four subdirectories: 
   .git
   bacula
   regress
   gui

To subsequently update it to the latest code, do:

   cd xxx
   git pull

Hopefully we will get commiting developers online early next week.  In 
addition to being a somewhat rushed move, this change has broken the normal 
nightly regression tests, which must be upgraded to pull from git rather than 
the SVN :-(

Any developer who wants to update the docs project of Bacula can do so using 
his existing SVN download.

Sorry for this inconvenience.

Best regards,

Kern

PS: To top it off I will be out every day next week except Tuesday, so please 
have patience ...


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users