I hear you. I use Fossil all the time for my own projects, and the
simple install and setup is great. It's just not the tool to use for
large scale projects with a hundred or more accounts, diverse access
control requirements, large non-code assets to store, and tricky
regulatory requirements on to
On Thursday 26 March 2009 13:25:38 Ge' Weijers wrote:
> > Doesn't git also have the ability to PGP-sign check-ins? I seem to
> > remember reading that, though I have never actually tried to do it.
>
> PGP key management is problematic in an enterprise environment.
> Authenticating against an LD
PGP key management is problematic in an enterprise environment.
Authenticating against an LDAP/Active Directory server is a whole lot
easier.
Gé
D. Richard Hipp wrote:
> On Mar 25, 2009, at 11:03 AM, Gé Weijers wrote:
>
>> Another issue is regulatory: sometimes you need to know who committe
D. Richard Hipp wrote:
>
> fossil setting pgp-command off -global
>
>
It seems that creating a new branch ignores this flag.
Ge'
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/list
On Mar 25, 2009, at 12:31 PM, Stephan Beal wrote:
> On 3/25/09, Hugo Schmitt wrote:
>> BTW, how can I make fossil stop looking for gpg every time I commit ?
>> Currently I have to confirm that I want to commit anyway with a
>> 'y'es.
>
> IIRC the call is:
>
> fossil set clearsign 0
Yeah. I
On Mar 25, 2009, at 12:13 PM, Hugo Schmitt wrote:
> BTW, how can I make fossil stop looking for gpg every time I commit ?
> Currently I have to confirm that I want to commit anyway with a 'y'es.
>
fossil setting pgp-command off -global
The -global is optional, of course. Use it to turn of PGP
On 3/25/09, Hugo Schmitt wrote:
> BTW, how can I make fossil stop looking for gpg every time I commit ?
> Currently I have to confirm that I want to commit anyway with a 'y'es.
IIRC the call is:
fossil set clearsign 0
--
- stephan beal
http://wanderinghorse.net/home/stephan/
_
BTW, how can I make fossil stop looking for gpg every time I commit ?
Currently I have to confirm that I want to commit anyway with a 'y'es.
Thanks
On Wed, Mar 25, 2009 at 12:10 PM, D. Richard Hipp wrote:
>
> On Mar 25, 2009, at 11:03 AM, Gé Weijers wrote:
> >
> > Another issue is regulatory: s
On Mar 25, 2009, at 11:03 AM, Gé Weijers wrote:
>
> Another issue is regulatory: sometimes you need to know who committed
> what and when, for auditing purposes.
This is why I gave fossil the ability to PGP sign check-ins. If a
check-in is PGP-signed, you have high confidence of who created i
Git and Fossil are different tools for different purposes. Git was
written for developing the kernel, and if you project fits into the same
mold it does very well. The UI issues have gotten better.
At my place of work we've looked at distributed SCMs, but we have *lots*
of graphical assets to stor
On Mar 24, 2009, at 10:52 PM, bharder wrote:
>
> http://keithp.com/blog/Repositor_Formats_matter/
>
> Would anybody knowledgeable care to comment about fossil in this
> light?
Both Havoc's original remarks (in favor of subversion) and Keithp's
rebuttal (in favor of Git) are old. Fossil exi
Link: http://keithp.com/blog/Repository_Formats_Matter/
On Tue, Mar 24, 2009 at 11:52 PM, bharder wrote:
>
> http://keithp.com/blog/Repositor_Formats_matter/
>
> Would anybody knowledgeable care to comment about fossil in this light?
>
> --
>
> Brad Harder,
> Method Logic Digital Consulting
> ht
http://keithp.com/blog/Repositor_Formats_matter/
Would anybody knowledgeable care to comment about fossil in this light?
--
Brad Harder,
Method Logic Digital Consulting
http://www.methodlogic.net
___
fossil-users mailing list
fossil-users@lists.fossi
13 matches
Mail list logo
