Re: [fossil-users] why would you give out only clone rights?

2010-11-02 Thread Joshua Paine
On 11/02/2010 04:28 AM, Rene wrote:
 I have some one who wants to clone my repo.
 If one just want source code then the Time line, Zip Archive is your option.

If they want the history, too, then cloning is the way to get it without 
having to come back to your site all the time.

-- 
Joshua Paine
LetterBlock: Web applications built with joy
http://letterblock.com/
301-576-1920
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] why would you give out only clone rights?

2010-11-02 Thread Rene


On Tue, 2 Nov 2010 07:35:06 -0400, Richard Hipp  wrote: 

On Tue, Nov
2, 2010 at 4:28 AM, Rene  wrote:

I have some one who wants to clone my
repo. But does that make sense? Clone alone allows you to just clone the
repo. But If I'm a remote developer and want to develop I need clone
rights. Because before I can develop I need to clone. 

If one just
want source code then the Time line, Zip Archive is your option. 

Do I
err some where?  
Some people may want to maintain a private branch of
your code, using a procedure similar to the one described at
http://www.sqlite.org/privatebranch.html [2]   

But how do you give
this permission to clone to every one. My solution was to add clone to
the user nobody. 

I can not oversee if this is to broad or which other
solution i should choose 

-- 
Rene
 

Links:
--
[1]
mailto:renew...@xs4all.nl
[2] http://www.sqlite.org/privatebranch.html
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


Re: [fossil-users] why would you give out only clone rights?

2010-11-02 Thread Richard Hipp
On Tue, Nov 2, 2010 at 7:54 AM, Rene renew...@xs4all.nl wrote:

 On Tue, 2 Nov 2010 07:35:06 -0400, Richard Hipp d...@sqlite.org wrote:



 On Tue, Nov 2, 2010 at 4:28 AM, Rene renew...@xs4all.nl wrote:

 I have some one who wants to clone my repo. But does that make sense?
 Clone alone allows you to just clone the repo. But If I'm a remote
 developer and want to develop I need clone rights. Because before I can
 develop I need to clone.

 If one just want source code then the Time line,  Zip Archive is your
 option.

 Do I err some where?

 Some people may want to maintain a private branch of your code, using a
 procedure similar to the one described at
 http://www.sqlite.org/privatebranch.html

 But how do you give this permission to  clone to every one. My solution was
 to add clone to the user nobody.


Correct.  Give clone privilege to user nobody and everybody can clone
without password or login.


 I can not oversee if this is to broad or which other solution i should
 choose

 --
 Rene


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users