[Sputnik-list] gitorious (was: proposed versium modifications)

pierre pracht pierre.pracht at gmail.com
Fri Mar 7 09:21:29 GMT+2 2008


Le 7 mars 08 à 11:29, Yuri Takhteyev a écrit :

>> An answer about repository layout ?
>> Need to make a choice :
>> - actual  : /alpha/lua/alphamod/init.lua
>
> Actual.

Ok
With git it's a no-brainer to move file around, so if you change your  
mind later ;)

>> Feel free to create your clones and submit merge requests.
>> Would you allow committer to your repository, no harm as git never  
>> delete
>
> Yes, but there is a bug in gitorious in the "Add Committer" path.
> Emailed Johan.

No harm, git should make easy to submit patch in the mean time.

>> anything. So we can setup branch in it who would be pulled with it  
>> (versium
>> refactoring). While keeping master branch clean (coherent and working
>> modules).
>
> Yes, when I star the changes.

Ok

>> An alternative is to setup clone for dedicated project. And share  
>> those
>> clone among us (as committer).
>
> Is there much practical difference between the two in terms of ease of
> merging?  A "clone" is more visible in gitorious.

Well, need to be used to get an idea.
If I didn't mistake git usage :
- if you make a several branch in a network repository, all will be  
pulled when you clone it.
- if you make several clone, developer may keep a single local git  
repository
   - need to be tested :
     http://www.kernel.org/pub/software/scm/git/docs/git-remote.html
   - not evident at first sight, need to be clearly documented
   - is a good way to go as you would be able to keep master branch  
closed
   - must not be mistaken as a locking, if developer use only local  
branch, nobody can follow their work. Better to publish all work in  
progress.
   - I don't know if gitorious use RESTful, but it would be cool to  
make a script who make a clone on gitorious and a local branch. (and  
more easy a script to bring a clone as a local branch)

That's why I was thinking that a single clone with many branch would  
have been more easy.
A middle way would be :
   - finish to clean actual git repository
   - make a development clone, and bring every one in it.
       - People making local and shared branch at will.

- pierre

  
      


More information about the Sputnik-list mailing list