-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
Last night I decided to convert one of my larger, unreleased projects to
Fossil, and to try a soft launch to see how I like it. Only, my
conversion process was somewhat convoluted, and I have this fear that
while it looks OK in the web
On Thu, Sep 9, 2010 at 6:52 AM, Nolan Darilek no...@thewordnerd.infowrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
Last night I decided to convert one of my larger, unreleased projects to
Fossil, and to try a soft launch to see how I like it. Only, my
conversion process was
On Thu, Sep 9, 2010 at 8:33 AM, Nolan Darilek no...@thewordnerd.infowrote:
Any thoughts on why I can't check out the first, empty commit? I just
tried on another test repository and it works fine, but in
http://dev.thewordnerd.info/hermes I'm told that it isn't a commit.
It seems that the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/09/2010 07:43 AM, Richard Hipp wrote:
It seems that the is_a_version() function used to determine if the thing
you are trying to checkout really is a checkin, works by looking to see if
the object has ancestors or children. (It used to only
On Thu, Sep 9, 2010 at 9:48 AM, James Peverill
arsenix.accou...@gmail.comwrote:
On 09/09/2010 09:26 AM, fossil-users-requ...@lists.fossil-scm.org wrote:
Fossil never generates a 401 error. The 401 Authorization Required
message is coming from someplace else. Are you sure your webserver is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wow, thanks for the quick feature! At first glance it seems to work.
I'll make some commits later today or this week and report back if
anything should break.
On 09/09/2010 08:59 AM, Richard Hipp wrote:
On Thu, Sep 9, 2010 at 9:25 AM, Nolan Darilek
On 09/09/2010 10:03 AM, Richard Hipp wrote:
I see. Right - fossil sync does not have any idea how to do LDAP
authentication.
AFAICT, mod_ldap lets Apache use an LDAP directory for authentication
information instead of a .htpasswd file. So if I'm reading right, fossil
sync wouldn't need to
I see. Right - fossil sync does not have any idea how to do LDAP
authentication.
I guess LDAP credentials are stored in the browser somehow. But fossil
sync bypasses the browser completely. So I guess it will somehow need
to
understand some kind of LDAP authentication protocol and
Hi,
I'm trying to tidy up a build directory after I mistakenly added a
bunch of temp build files. So I did:
699 terms-win fossil rm build
DELETED build/Debug/terms-win
DELETED build/terms-win.build/Debug/terms-win.build/build-state.dat
DELETED
Am 09.09.2010 um 16:03 schrieb Richard Hipp:
On Thu, Sep 9, 2010 at 9:48 AM, James Peverill arsenix.accou...@gmail.com
wrote:
On 09/09/2010 09:26 AM, fossil-users-requ...@lists.fossil-scm.org wrote:
Fossil never generates a 401 error. The 401 Authorization Required
message is coming
On 09/09/2010 03:54 PM, fossil-users-requ...@lists.fossil-scm.org wrote:
1. Trust a front end webserver like apache and what it sets in the
REMOTE_USER cgi variable (you could use Kerberos/SPNEGO Auth that way too,
same principle if you used mod_kerb).
This is what we have been doing
11 matches
Mail list logo
