I've used fossil for years now with lots of commits to trunk and very few
very simple branches which tend to get merged right into trunk after only a
few commits. I have managed to get myself in a confusing place with one of
my projects.
Essentially what I did was to commit a change to a new
Like Andy, I'm sure I've read that file names are what gets
tracked - and wasn't even aware anyone had worked on a
directory rename function ... At times when a project
grows, I do tend to create new subproject directories and
move existing files to those directories - and a directory
rename
Oh, and THANK YOU for responding.
> On Dec 20, 2017, at 5:54 PM, Warren Young wrote:
>
>> On Dec 20, 2017, at 3:40 PM, dewey.hyl...@gmail.com wrote:
>>
>> # ls -lh /fossils|grep fossil
>> -rw-rw-rw-1 1000 root 272.0K Dec 19 14:37 archsetup.fossil
>> -rw-rw-rw-
All users have read/write permissions on those files, so this doesn’t make
sense (to me) from a Unix permissions standpoint.
I am indeed a BSD guy, but ... in reality fossil is running in a docker
container on a Linux server and accessing the files via sshfs mount. I can futz
about and make
<d...@sqlite.org> wrote:
>
>> On 9/15/17, Dewey Hylton <dewey.hyl...@gmail.com> wrote:
>> just for completeness ... i verified that i am seeing the same address
>> during a commit:
>>
>> Autosync: https://redacted
>> Round-trips: 1 Artifacts
just for completeness ... i verified that i am seeing the same address
during a commit:
Autosync: https://redacted
Round-trips: 1 Artifacts sent: 0 received: 0
Pull done, sent: 390 received: 994 ip: 2.0.1.187
New_Version: 906246b7cd7e5fec91c69502981582bdbfc0a89e
Autosync: https://redacted
I predict this to be the best email I receive today.
My first thought was "This is like paid support!"
My second thought was "Wait ... paid support has *never* been this good ..."
Thanks for your work!
On Thu, Aug 17, 2017 at 10:10 PM Andy Goth wrote:
> On 08/16/17
t-description\", \"${pdesc}\", now());"
%-=
next steps for me are to pre-populate a README.md, commit, and have /home
referencing that.
thanks again for your help!
On Thu, Jan 21, 2016 at 11:26 AM, Dewey Hylton <dewey.hyl...@gmail.com>
wrote:
> the "most official&
i suppose banging out some sql wouldn't be out of the question, though i
had not thought of this. it makes perfect sense, though. if i get stuck
i'll ask to see what you came up with. thanks for the suggestion!
On Wed, Jan 20, 2016 at 11:50 PM, Scott Robison
wrote:
> On
the "most official" way is exactly what i was looking for, and i did miss
the export/import features. the template feature doesn't appear to do all
i'd like (such as modifying the project description). export/import for my
purposes would be fiddly because of the byte counts and such. perhaps the
From: Andy Bradford
amb-sendok-1430461727.niogihkppihojgmic...@bradfords.org
To: Dewey Hylton dewey.hyl...@gmail.com
Cc: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org
Sent: Wednesday, April 1, 2015 2:28:46 AM
Subject: Re: [fossil-users] using fossil server --repolist behind
From: Dewey Hylton dewey.hyl...@gmail.com
To: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org
Sent: Sunday, March 29, 2015 11:07:31 AM
Subject: Re: [fossil-users] using fossil server --repolist behind nginx
proxy
From: David Macek david.mace...@gmail.com
Sent: Sunday
From: David Macek david.mace...@gmail.com
Sent: Sunday, March 29, 2015 10:56:07 AM
On 29. 3. 2015 16:55, Andy Bradford wrote:
Given that you're using nginx as a proxy, perhaps you need to add
--baseurl to the fossil server options?
OP mentioned that he tried it.
yeah ... that
i have the following running to serve a directory full of fossil archives:
/usr/bin/fossil server --repolist --port 8181 /data/fossil
this appears to work perfectly when directly hitting the site:
http://fossil.server.local:8181/
http://fossil.server.local:8181/somefossil
14 matches
Mail list logo