The SALOME team is pleased to announce that the access to the SALOME sources git repositories is now available.

These repositories provide read-only access to the daily development snapshots of all SALOME modules sources.

The full list of available git repositories and other helpful information can be found at the repositories list page.

W*O*W! This news makes my day! This is a *huge* deal!

I just try the test command:

git clone http://git.salome-platform.org/KERNEL_SRC.git

And have the error messages:

Initialized empty Git repository in /net/jabba/home2/letexier/CAD/OCC/SALOME/KERNEL_SRC/.git/

error: couldn't connect to host while accessing http://git.salome-platform.org/KERNEL_SRC.git/info/refs

fatal: HTTP request failed

Help me !?

Hi Paul,

I suspect that you are behind a proxy. Don't forget to setup your HTTP_PROXY environment variable before using the git command.

to a GIT repository makes the whole history kind of useless! That's more of a backup strategy than a source-code repository which should track and document the development in a "who did what, when and why" fashion. Especially, the information contained by a commit object is greatly reduced since it is difficult to separate unrelated changes from one another. They are just squashed into one big snapshot commit instead. This completely cripples the potential of GIT. Sorry to say so, but I'm very disappointed.

Hi Etienne

You're right, I've to setup GIT to work with an HTTP proxy. Now it works !

My HowTo (for git version 1.7.0.2) is:

1. %git config --global --add http.proxy http://your.proxy.server:port/      # Ask your Sys. Admin.
   
2. %cat /home/cea/letexier/.gitconfig                                                         # See/Verify
   [http]
           proxy = http://132.165.77.2:3128/
   
3. %git clone http://git.salome-platform.org/KERNEL_SRC.git
   Initialized empty Git repository in /home/cea/letexier/SALOME/KERNEL_SRC/.git/
4. %ls KERNEL_SRC                                                                                  # Only one file, read it !
   README
5. %git checkout -b V5_1_main origin/V5_1_main
   Checking out files: 100% (1210/1210), done.
   Branch V5_1_main set up to track remote branch V5_1_main from origin.
   Switched to a new branch 'V5_1_main'
6. %git gui
   

Just before checkout I've done:

1. %cd KERNEL_SRC/
2. %git branch
   * V5_1_main
     master
3. %git branch -a
   * V5_1_main
   master
   remotes/origin/HEAD -> origin/master
   remotes/origin/V5_1_main
   remotes/origin/master

Everyday GIT With 20 Commands Or So

Just an advice to new GIT user MUST read "Everyday GIT With 20 Commands Or So" (http://www.kernel.org/pub/software/scm/git/docs/everyday.html).

Everyday GIT With 20 Commands Or So

Everyday GIT With 20 Commands Or So

Everyday GIT With 20 Commands Or So

Everyday GIT With 20 Commands Or So

Add to this http://www.kernel.org/pub/software/scm/git/docs/gitworkflows.html

Michael> Maybe because those git repositories are just limited copies of the CVS bases which are currently used in the project...

Two options:

- http://www.kernel.org/pub/software/scm/git/docs/git-cvsimport.html

- http://cgit.freedesktop.org/~krh/parsecvs/

We appreciate you concern about those git repositories.

You can be sure that the solution proposed in your links were studied.

What you are not aware of is that all the CVS bases of the project cannot be just copied to the public git repository. There are some legal issues concerning a part of the sources.

The final solution proposed here is the best compromise we found to offer a daily access to the SALOME sources by using the GIT tool.

Sorry if this solution is disappointing you but currently this is the best solution for a read-only access to the sources.

Version 5.1.4 not yet in GIT repositories ?

cd KERNEL_SRC/
git branch -a
* master
  remotes/origin/HEAD -> origin/master
  remotes/origin/V5_1_main
  remotes/origin/master

It seams to me that a specific branch should appears.

Why isn't it an image of the real SALOME repository ?

Hi administrator,

After reading this article in Kitware blog about their recent switch to GIT, and the use of the tool Gerrit to ease code review and project management. One of the advantage highlighted is "One of the distinct advantages of distributed version control is that you can push your commits to multiple places, or remotes." and I thought it might interest the Salome consortium.

Bests,

Pierre