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
This patch should fix that
On Wed, 2009-03-25 at 20:05 -0700, Ge' Weijers wrote:
> D. Richard Hipp wrote:
> >
> > fossil setting pgp-command off -global
> >
> >
> It seems that creating a new branch ignores this flag.
>
> Ge'
>
> ___
> fossi
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 Wed, Mar 25, 2009 at 9:55 PM, D. Richard Hipp wrote:
> It is a little more complicated than that, though. The way the built-
> in server for fossil works is that it starts a new child process for
> each incoming request. So somehow the child process that handles the
> request has to notify th
On Mar 25, 2009, at 4:48 PM, Hugo Schmitt wrote:
> What about allowing the client (a setting that would default to off,
> of course) to send a "remote-close" ?
>
Yes. I think that is the right approach.
It is a little more complicated than that, though. The way the built-
in server for fos
What about allowing the client (a setting that would default to off, of
course) to send a "remote-close" ?
On Wed, Mar 25, 2009 at 5:34 PM, D. Richard Hipp wrote:
>
> On Mar 25, 2009, at 3:22 PM, Hugo Schmitt wrote:
>
> > An alternative would be to add an option to the server command, say
> > "
On Mar 25, 2009, at 3:22 PM, Hugo Schmitt wrote:
> An alternative would be to add an option to the server command, say
> "-single", that would automatically stop the server after the first
> pull/push command. So we could just run "fossil server repo.fossil
> &", and then push/pull on the
An alternative would be to add an option to the server command, say
"-single", that would automatically stop the server after the first
pull/push command. So we could just run "fossil server repo.fossil &", and
then push/pull on the same xterm window... simplifying the scripts.
Cheers,
Hugo
On T
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/
_
On 3/25/09, Rene de Zwart wrote:
> I'm not sure what you mean by fossil-compatible markup.
fossil supports a subset of HTML, but explicitly disallows (and
silently elides) certain elements or attributes.
>2. Bullets are "*" surrounded by two spaces at the beginning of the line.
> No but noth
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
18 matches
Mail list logo
