I use a password generator of my own design - basically takes the userid,
concatenated with a fairly long secret phrase, and then I do SHA1 and
convert it to base64, giving a password like:
Acgq75VpCWjdsJaa5abe9JeX3I (don't worry, this isn't a real password to
anything)
After Warren's comment
I like it, though the timing is pretty fast, and some slides are truncated.
On 9 July 2018 at 12:06, mario wrote:
> As followup to last month` Show time.. discussion:
>
> → http://fossilslideshow.tmp.include-once.org/
>
> (Take in mind this ain't a mockup yet; just as example.)
>
> Why oh why?
>
t 11:50, Warren Young wrote:
> On Jul 2, 2018, at 9:38 PM, David Mason wrote:
> >
> > It's pretty common to put classes on tags, to use CSS to
> conditionally choose different renderings by simply changing the class of
> the body tag.
>
> I think you’d have to writ
It's pretty common to put classes on tags, to use CSS to
conditionally choose different renderings by simply changing the class of
the body tag.
../Dave
On 3 July 2018 at 00:23, mario wrote:
> Mon, 2 Jul 2018 17:20:17 -0600 Warren Young :
>
> > Under what conditions would you have two differen
Great! Thanks.
On 29 June 2018 at 02:24, Warren Young wrote:
> On Jun 28, 2018, at 8:53 PM, David Mason wrote:
> >
> > Looks nice. What I meant was: what do I have to change to make it work.
>
> Clone my repository, go into Fossil UI, then navigate to Admin > Ticke
Looks nice. What I meant was: what do I have to change to make it work.
Thanks ../Dave
On 28 June 2018 at 18:33, Warren Young wrote:
> On Jun 28, 2018, at 6:15 AM, David Mason wrote:
> >
> > where did you make these changes?
>
> It’s most readily seen in this repo
Warren, this looks great! Apologies for not knowing, but where did you make
these changes?
On 28 June 2018 at 04:11, Warren Young wrote:
> On Jun 27, 2018, at 8:16 AM, Richard Hipp wrote:
> >
> > If I leave [a feature request ticket] open, then
> > people become alarmed at all the open bugs aga
On 27 June 2018 at 11:16, Richard Hipp wrote:
> If a feature request comes in via ticket, I can either leave the
> ticket open for some future date when I might implement the idea, or I
> can close it immediately as "not a bug". If I leave it open, then
> people become alarmed at all the open bu
It does seem a bit strange that we all sell the value of fossil partly
because it has a wiki and ticket system built in. but then we don't eat
our own dog food.
I'm no better on my personal projects... but perhaps RSS can also play a
role here. Or if one could subscribe to the email updates fo
There is nothing wrong with a C library handling its internal processing
using setjmp/longjmp, as long as there's no C++ callbacks or any other way
that C++ code that might use throw/catch can be executed from within calls
to that library.
It's a little bit more work than just replacing the calls
I was thinking it would be a little more than this, but perhaps:
# define FOSSIL_EXIT(n) (api_exit_status-=n,longjmp(blabla))
would actually be enough.
And a similar setjmp-calling macro at the beginning of each API function
would be all that would be required there.
../Dave
On 25 June 2018
ote:
> On Sun, Jun 24, 2018 at 11:19 PM David Mason wrote:
>
>> I really don't understand the reticence to use setjmp/longjmp to turn all
>> of these short-cut exits into library return-to-API trampolines. It
>>
>
> To be clear: that's my reticence, not Richar
I really don't understand the reticence to use setjmp/longjmp to turn all
of these short-cut exits into library return-to-API trampolines. It would
allow you to retain all the existing fossil codebase. Rewriting the code
into library form is an interesting project, but it seems like a huge
amount
Just had a quick thought that might make the conversion to library much
easier.
If you have a relatively small API interface, each of the API functions
could do a setjmp https://en.wikipedia.org/wiki/Setjmp.h and then the fatal
error routines could longjmp back. This would give you API safety, at
seems to be the leading excuse - other than "it's not GIT".
../Dave
On 15 June 2018 at 13:35, Richard Hipp wrote:
> On 6/15/18, David Mason wrote:
> > I heartily agree with this... A flag to allow a person (including
> > Anonymous) to make a commit that would automat
I heartily agree with this... A flag to allow a person (including
Anonymous) to make a commit that would automatically go into a new branch
like "Patch-1" (each one incrementing the branch number) is (a) better than
emailed patches, and (b) better than pull requests. Primarily because it
puts it in
This is very funny looks a lot like the real thing:
https://git-man-page-generator.lokaltog.net/
but it's auto-generated on the fly!
../Dave
On 14 April 2018 at 07:49, Richard Hipp wrote:
> On 4/14/18, Svyatoslav Mishyn wrote:
> > (Sat, 14 Apr 06:22) Richard Hipp:
> >> Article: https
Days since start of the release branch would seem like a good proxy -
assuming you create release branches (which seems like a good idea):
1) increasing
2) small number - you could use hours instead of days if you release
multiple versions per day
3) pretty directly mappable to a commit.
4) same on
Why not support --dryrun and --dry-run but only document the former? Then
scripts won't break. It's not like anyone is going to accidentally use
--dry-run to mean something else.
../Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
h
On 16 December 2017 at 20:33, Andy Bradford
wrote:
> Thus said David Mason on Sat, 16 Dec 2017 15:36:51 -0500:
>
> > I tried to add a tag to my fossil. After looking at the documentation
> > which said:
>
> The ``fossil tag'' command is for very low-lev
he gory details.
On 16 December 2017 at 16:52, Richard Hipp wrote:
> On 12/16/17, David Mason wrote:
> > Can I back those out any way short of re-cloning the remote fossil?
>
> You can "cancel" the old tags so that they don't have any effect. You
> should see &qu
Can I back those out any way short of re-cloning the remote fossil?
On 16 December 2017 at 16:10, Richard Hipp wrote:
> On 12/16/17, David Mason wrote:
> > I tried to add a tag to my fossil.
>
> I didn't write the "fossil tag" command - that is contributed co
I tried to add a tag to my fossil. After looking at the documentation which
said:
I did the following:
: ~/fs/Optijava ; fs tag add -n --user-override shruthi pre-dissertation
e5b61ea041
not found: pre-dissertation
: ~/fs/Optijava ; fs help tag|less
: ~/fs/Optijava ; fs tag add -n --user-override
I would like yesterdays with a bit of whitespace between commit comments.
Also someone liked the original because the checkin tag was in a
predictable place. If you put the tag last in the extra information it
would be predictably at the right margin.
On 27 November 2017 at 21:01, Richard Hipp
Does it stay that size with moderate activity, or does it start growing
significantly? Does the pack format slow it down, or speed it up?
Given that the Git version only has 93% of what the Fossil repo has, I'd
say Fossil is doing quite well.
../Dave
On 27 November 2017 at 16:16, Joerg Sonnenber
I use symlinks *very* heavily. Almost exactly 10% of the files in my main
fossil hierarchy are actually symlinks. Fossil not supporting them would be
a huge drawback for me. Good support for symlinks and nested repositories
are 2 of the details I like best about Fossil (in addition to the obvious
f
On 26 November 2017 at 16:52, Ron W wrote:
> I think there needs to be some indication that there is more information.
> From my experience, an ellipses is a very common tool for this purpose - as
> long as they are visible.
>
I agree. I really think tooltips (titles) should be used as well as t
What you have seems to handle the ellipsis properly (by my definition of
properly).
But you really should use title/tooltip.
On 25 November 2017 at 21:45, Richard Hipp wrote:
> On 11/25/17, Richard Hipp wrote:
> > On 11/25/17, sky5w...@gmail.com wrote:
> >> Ok, the current behavior is cool, b
ky the above works on
Chrome/Firefox but shows a space on IE/Safari - see:
https://stackoverflow.com/questions/5881954/html-stop-child-elements-from-inheriting-parents-title-attribute
but you might have a useful title to give it.
../Dave
On 25 November 2017 at 20:47, Richard Hipp wrote:
>
Looks good.
When I did that, I made clicking on anywhere in that div expand it.
You should also add a title that says "Click to expand" so that they don't
have to know/infer that the ellipsis is an active link.
I also like being able to shrink it back... right now there isn't that much
extra det
:ellipsis;
}
The optional expand parameter to toggleExpand is if you want to add a
different class when it's expanded. I use it elsewhere, but not here.
../Dave
On 25 November 2017 at 09:38, David Mason wrote:
> 1) Add/remove a class to an enclosing DIV. You can see a very simple
>
1) Add/remove a class to an enclosing DIV. You can see a very simple
version that I wrote in action on https://programmingfortherestofus.com
click on the bullets under Elevator Pitch.
2) Include all the content, just don't display it by default... dynamically
downloading additional content is almo
I like the B cases... in fact I'd indent the details a bit so that the
comments are easier to find visually.
On 24 November 2017 at 11:53, wrote:
> I understand the need for links, but do users really need truncated hashes
> for every line?
> Can the link be applied more subtly?
> Can there be a
Also as a mere fossil user, I would find it useful if fossil could respond
to a git client and serve files. I use Pharo, which is working toward
integrated support for git, but I'd much rather trust my bits to Fossil.
While the Fossil UI is nice, I see much less value in using a local Fossil
to acc
16:04, Richard Hipp wrote:
> On 9/28/17, David Mason wrote:
> >
> > Last question for a while: in clone.c line 104 it says to use %40, %2f
> and
> > %3a for special characters in the userid and password (for obvious
> > reasons). Are there any other restrictions on
sword (for obvious
reasons). Are there any other restrictions on the repo name or other parts
of the URL?
Thanks ../Dave
On 28 September 2017 at 09:53, Roy Keene wrote:
> On Thu, 28 Sep 2017, Mark Janssen wrote:
>
>
>>
>> On 28 Sep 2017 13:37, "David Mason"
No, just setuid something other than www - an ordinary user.
I'm currently doing a workaround to not run fossil from within a CGI, but
it's not optimal (exposes some information I'd rather not expose).
Thanks
On 28 September 2017 at 09:26, Richard Hipp wrote:
> On 9/28/17,
On 28 September 2017 at 07:37, David Mason wrote:
> I wasn't clear! (I've been working all night on this so it's
> understandable.)
>
> I have all the logic I need I just want fossil to behave like it would
> at a terminal prompt, rather than acting like a CGI... the
r
the record this is Linux.
Thanks ../Dave
On 28 September 2017 at 06:37, Richard Hipp wrote:
> On 9/28/17, David Mason wrote:
> >
> > I need to create fossils on the fly [using CGI]
>
> Fossil does not (currently) have that capability.
>
> What you are really asking for i
to create fossils on the fly
and change permissions/passwords, etc.
Thanks
On 26 September 2017 at 12:01, David Mason wrote:
> This is proxy, not CGI, but the same appears to apply:
>
> fossil clone http://dmason%40ryerson.ca@localhost:8081/f2017/A-dmason_
> ryerson.ca x.fossil
>
hough obviously you won't be changing it!!!
Thanks again (both for the immediate help, and for fossil itself)!
../Dave
On 26 September 2017 at 10:05, Richard Hipp wrote:
> On 9/26/17, David Mason wrote:
> > Indeed! Thanks... I already noted that in the web access, but the file
> d
On 26 September 2017 at 06:30, Richard Hipp wrote:
> On 9/26/17, David Mason wrote:
> > if I try:
> >fossil clone
> > https://dmason%40ryerson...@cps506.scs.ryerson.ca/fossil/
> f2017/A-dmason_ryerson.ca.fossil
> > foo.fossil
> > it prompts for pass
On 25 September 2017 at 13:59, Richard Hipp wrote:
> On 9/25/17, David Mason wrote:
> > I am trying things differently this year. I want to use one instance of
> > fossil running proxied behind a firewall. I have the following in my
> > Apache conf file:
> >
>
I am trying things differently this year. I want to use one instance of
fossil running proxied behind a firewall. I have the following in my
Apache conf file:
ProxyPass http://127.0.0.1:8081
ProxyPassReverse http://127.0.0.1:8081
SetOutputFilter proxy-html
On 8 September 2017 at 10:47, Thomas wrote:
> If I do this I can never use addremove again. The checkin script runs
> addremove automatically each time.
>
If it's in the ignore-glob file, addremove won't add it. So put in the
ignore-glob, remove it once, clean up the shun, commit, and then what
On 29 August 2017 at 23:55, Andy Goth wrote:
> I'm curious how the Markdown formatter would know what language rules to
> use for syntax highlighting, so surely there's more to the syntax than
> bracketing ("fencing") the code with lines consisting entirely of "```".
> I searched online and found
I've seen it too, but it's sporadic. My crontab pull script now checks if
the size is 0 and ignores the file if so.
../Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-
It is unclear from the documentation what this switch actually does, and I
unfortunately do not have time at the moment to read the code.
I use Linux and MacOSX and use symlinks to directories very heavily, so am
a little worried about what this change does. I never explicitly use this
switch.
I
Wow... longest thread I've ever seen. I scanned through and didn't see
mention of the simplest solution, if you have shasum available.
> shasum urltags.js
1bea11bf4a97b012e7d8b17c71a7d444f0b5a5aa
> fossil ui
Then go to localhost:8081/artifact/1bea11bf4a97b012e7d8b17c71a7d444f0b5a5aa
and you'll g
n 14 June 2017 at 01:41, David Mason wrote:
> `fossil uv list` doesn't mention any path information. Does it have path
> information behind the scenes so that `fossil uv revert` can put the file
> in the original place?
>
> Is there a way to find if any unversioned file has
files?
Thanks ../Dave
On 14 June 2017 at 01:32, David Mason wrote:
> I finally got around to this, but I got the following errors on Linux:
> : ~/Sites/p4ru/kitPJS ; fossil unversioned revert
> Usage: fossil sync URL
> : ~/Sites/p4ru/kitPJS ; fossil ver
> This is fossil version 2
`fossil unver revert`). It's good that cat
works, but revert seems nicer!
Thanks ../Dave
On 10 May 2017 at 09:34, David Mason wrote:
> Perfect! I knew it would be easy.
>
> Thanks
>
> On 10 May 2017 at 07:04, Richard Hipp wrote:
>
>> On 5/10/17, David Mason wrote:
You can have a working directory for one repository nested inside a folder in a
working directory of another repository. See the —nested option for `fossil
open`.
I use this *extensively*. It’s very convenient. But it may not be quite what
you want because you do have to commit separately for
On 10 May 2017 at 17:05, Artur Shepilko wrote:
> Not sure about the objectives the students are learning in this
> course, but if it in any way relates to programming, recognizing as
> to what to keep under version control is a reasonable objective on its
> own.
>
While I might agree, and the t
Bradford wrote:
> Thus said David Mason on Wed, 10 May 2017 01:07:22 -0400:
>
> > If the students were very disciplined, they would assiduously edit
> > ignore-glob to prevent this. But if there is one thing that students
> > (en-mass) are not, it's disciplined!
>
when
they first clone the repo their local repo gets the configuration.
../Dave
On 10 May 2017 at 07:11, Richard Hipp wrote:
> On 5/10/17, David Mason wrote:
> > I've described before how I use fossil to manage student assignment
> > submissions in courses I teach.
>
Perfect! I knew it would be easy.
Thanks
On 10 May 2017 at 07:04, Richard Hipp wrote:
> On 5/10/17, David Mason wrote:
> > I have a fossil repo and in it I have a file foo.js that is generated by
> my
> > build process - so I don't want it versioned. But I *do* want
I've described before how I use fossil to manage student assignment
submissions in courses I teach.
A perennial problem is that the students commit binary executables, .o
files, and the like. Theses change every build so I have dozens of versions
of potentially large files in the student repos. D
I have a fossil repo and in it I have a file foo.js that is generated by my
build process - so I don't want it versioned. But I *do* want it
distributed, and want it referencable from foo.html - which *is* versioned.
foo.html and foo.js are *not* served by fossil, but by a simple apache or
nginx se
On 7 May 2017 at 12:20, John Pateman wrote:
>
> The right click commit seems to work fine in Sierra. You need to add the
> checkout directory to the list that SnailFossil is tracking. The files that
> are synced up should all have a green tick badge. Adding a new file to the
> checkout folder sho
I bought this, largely to support the Fossil community (because I don't use
Finder much, but this might change my workflow), and a couple of points:
1) the docs are wrong... to add a working directory you need to go to
SnailFossil preferences.
2) The right-click to commit doesn't do anything for
On 18 April 2017 at 18:04, Ross Berteig wrote:
>
> No, the wild cards in the glob can match any part of the path. You can
> ignore "*/_build/*" and that will ignore any folder named _build and all
> its descendants anywhere in the tree except at the root of the workspace.
But if I want to *not*
I have had to use Git for something this semester. It was mostly a failure
and I'll find a way to use fossil going forward.
That said, I noticed one feature of Git that was very useful, and I'd love
to see in Fossil. In Git, you can have a .gitignore file in any directory
and it applies to that
Another option is to create a fossil for the 3rd party libraries, and then
open that fossil --nested in a directory inside your working directory.
Then nothing in that nested directory tree will be part of the main
fossil. You don't even need to commit to it if you don't want. Lastly,
when you do
I've been using fossil for several years now, so when I set up a new fossil
my first operation is to copy over an existing .fossil-settings and commit,
so I haven't been exposed to this problem for a while. I certainly
remember when I first used it that it did some unexpected things. Perhaps
if th
On 11 April 2017 at 14:34, Scott Robison wrote:
> No, it is an explicit command clearly stating the user's desire for
> exclusion of these files *that are not already under source control*.
> The fact that the user does not remember or did not realize they
> issues conflicting commands does not m
Richard and Warren both make very legitimate comments. I wasn't seriously
suggesting that work should stop moving Fossil forward for the perhaps
marginal benefit of conversion to Rust.
However, the value of Rust is not simply memory management. The
*considerably* more expressive type system, and
I's about 1/3 of the way through this report:
https://groups.google.com/forum/#!topic/mozilla.dev.version-control/nh4fITFlEMk
It seems that they originally preferred GIT (because it was what they knew)
but now prefer hg, although it's a bit light on the reasons. The article
points out that Facebo
identally trimmed when there are no other repos available
> with which to sink. Perhaps the trimmed content gets written into a
> separate "trash-can" database?
>
> On 7/26/16, David Mason wrote:
> > I have a problem.
> >
> > I use fossil for my courses - one
On 26 July 2016 at 17:13, Richard Hipp wrote:
> SELECT DISTINCT uuid
> FROM blob, mlink, filename
>
Works a charm (18 UUIDs show up). Now if there were a way to shun from the
command line, I'd be golden.
BTW, swapping "uuid" and "filename.name" in the SQL lists the files that
match a uuid.
Is there any way to find all the artifacts that correspond to a given
pathname? Then I could shun those.
On 26 July 2016 at 16:51, Richard Hipp wrote:
> On 7/26/16, David Mason wrote:
> > I have a problem.
> >
> > I use fossil for my courses - one I've used
I have a problem.
I use fossil for my courses - one I've used for 4 years. In each year
there are grades files (with student names, student numbers and grades),
and they get changed and committed over the semester, so there are many
versions in the fossil (hundreds of checkins).
I want to share
It's a strange name, but this website gives useful ranking of many things
over a variety of competing products.
Here is the version-control link: http://hammerprinciple.com/versioncontrol
Fossil does quite well along many of the vectors of comparison, but adding
your ranking would help.
../Dave
I submitted a patch to create a --mail-quiet option for update that is
quiet unless a change has happened. But it never made its way into trunk
(even though I sent the copyright form to Rich)
The comment for it reads:
The -m or --mail-quiet option suppresses status info unless there was
some cha
#x27;t actually used the bug-tracker yet, so I don't know what I'm
missing.
../Dave
On 7 April 2016 at 16:17, David Mason wrote:
> I just added
> http://www.slant.co/topics/1274/viewpoints/5/~acid-compliant-scalable-databases~sqlite
> and
> http://www.slant.co/topics/2727/v
I just added
http://www.slant.co/topics/1274/viewpoints/5/~acid-compliant-scalable-databases~sqlite
and
http://www.slant.co/topics/2727/viewpoints/8/~self-hosted-bug-trackers~fossil
on Slant.co
Others might be better placed to add pros and cons.
../Dave
___
A switch or setting to --perservemtime sounds like it would be easy to do,
and useful.
It would leave the default behaviour for legacy reasons but allow Zoltan
and others who are willing to do the make clean;make (like me) to have a
useful set of file times.
The nice thing would be that if you're
On 9 February 2016 at 15:56, Andy Bradford wrote:
> Are you allowing REMOTE_USER to work in your Fossils/dmason.fossil?
>
> $ echo "SELECT * FROM config WHERE name = 'remote_user_ok';" | fossil sql
> -R Fossils/dmason.fossil
>
Bingo! I had actually added this to my script last year
fossil s
On 9 February 2016 at 15:48, Richard Hipp wrote:
> A Fossil repository is an SQLite database, and you shouldn't create
> links (symbolic or hard) to SQLite databases.
>
Understood, but this is a very low-contention server. I'm really just
using symlinks here to demonstrate the problem.
I'll tr
As you may remember, I use fossil to have students submit assignments for
my courses. Last year it worked well (eventually) with some problems with
Windows.
I have 160+ students. All of their fossils are made by the same script
that creates a user with their ID and capabilities:v and a developer
Mac.
../Dave
On 26 March 2015 at 15:42, David Mason wrote:
> Me again... :-)
>
> I have a student running Windows using the current fossil as of January.
>
> 1) PLINK.EXE works so there's no ssh problem.
> 2) She has successfully committed before.
> 3) She tried to comm
On 3 November 2015 at 10:48, Eric Rubin-Smith wrote:
>
> On Tue, Nov 3, 2015 at 1:33 AM, Stephan Beal
> wrote:
>>
>> i can't speak for Richard, but if i had my way, fossil wouldn't support
>> symlinks at all.
>>
>
This would force me to stop using Fossil (or at least updating to a version
that d
On 16 September 2015 at 21:56, Steve Stefanovich wrote:
> Isn't the main annoyance the need to commit two times, one in nested
> checkout and one in the 'root' repo, and to try to keep timeline order in
> both?
>
> How do you guys manage that - prevent committing/cloning to root and
> always use
On 14 September 2015 at 13:58, Warren Young wrote:
> On Sep 12, 2015, at 9:54 AM, Oliver Friedrich <
> redtalonof+mailingl...@gmail.com> wrote:
> >
> > with nested repositories my administration overhead would exceed even
> the single repository solution, right?
>
> The alternative to managing ju
On 26 August 2015 at 04:27, Luca Ferrari wrote:
>
> Correct!
> Shame on me.
Not shame, at all! Some of the reasons for things are useful to think
about, and because a popular system (e.g. GIT) does it a particular way can
make us think it is the right way without thinking carefully. I didn't
On 21 August 2015 at 07:33, Martin Gagnon wrote:
> - Links in home page on each of your repos:
> - Open nested repository:
I do the nested one a lot (I have a Courses repo with common stuff for all
the courses I teach, and a nested repo underneath for each course).
The 3rd choice is a symbolic
On 4 August 2015 at 06:09, Stephan Beal wrote:
> On Tue, Aug 4, 2015 at 12:04 PM, Luca Ferrari
> wrote:
>
>> On Tue, Aug 4, 2015 at 11:31 AM, Stephan Beal
>> wrote:
>> > http://www.fossil-scm.org/index.html/help?cmd=/shun
>>
> In that case you would have to shun all of the files individually. F
A simple fix would seem to be to match *.fossil but not .fossil - in other
words, require a non-empty prefix to consider it a fossil.
../Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailm
I use Fossil in 2 ways with students.
1) for each research project I have a Fossil, and all Grad students working
on that project (and I) have commit access. There are few enough people
that it works out.
2) for assignments, I create a Fossil per student and the student plus the
marker(s) and I
Any improvement to the handling of symlinks gets my vote!
../Dave
On 7 May 2015 at 23:25, Abilio Marques wrote:
> +1. Been there, two times just in the last week (I need to sleep better).
>
> On Thu, May 7, 2015 at 7:51 PM, Andy Goth wrote:
>
>> I propose extending [fossil changes] to report w
Thanks for the examples, Andy.
I use symlinks a lot. I *really* wish fossil handled them "properly".
This is one of my biggest beefs about fossil.
The other big one is that if I set some property (in this case
allow-symlinks true) and I also set the corresponding .fossil-setting I get
a warning
What Scott says, abbreviated from the C FAQ:
http://c-faq.com/null/ptrtest.html
FWIW, I always use if(p) to verify a pointer is valid.
../Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mai
Here is another problem with symlinks:
Last login: Tue Apr 7 20:11:50 on ttys004
: ~ ; cd /tmp
: /tmp ; fs init foo.fossil
project-id: d24564a4337e8c50f77a20ee355e2f76a9b84b78
server-id: aa025469a22046732337b7fa075c7c4e85f45c0a
admin-user: dmason (initial password is "d5a283")
: /tmp ; cd
Me again... :-)
I have a student running Windows using the current fossil as of January.
1) PLINK.EXE works so there's no ssh problem.
2) She has successfully committed before.
3) She tried to commit and got a "Would fork" so
4) She did an update
5) then commit she got "Unable to write to standar
Problem 2 is similar to "fossil add filename" saying "ADDED: filename" even
if it was already known. This confuses novice users.
On 25 March 2015 at 16:44, wrote:
> This is on a Windows machine so, filenames are case insensitive.
>
> To reproduce (f = fossil):
>
> f new xxx.fossil
> f o xxx.f
Does the server fossil know the version number of the client fossil on a
clone? Or could it ask? If so, it could do what Andy suggests.
../Dave
On 16 March 2015 at 14:24, Richard Hipp wrote:
> On 3/16/15, Andy Bradford wrote:
> > Thus said Stephan Beal on Mon, 16 Mar 2015 18:41:34 +0100:
> >
Thank you Graeme for your thought-provoking post. It seems most
challenges and rebuttals have played out.
If anyone was mining this thread for ways to improve fossil, I think
they'd see 2 things:
1) Fossil's ticket handling is not best-in-class. What are the key
features that would make it at l
You have a typo in your post:
"only projects I use Git on are my own"
pretty sure you meant Fossil in that phrase.
On 13 March 2015 at 08:40, Graeme Pietersz wrote:
>
>
> On 13/03/15 08:17, jungle Boogie wrote:
>>
>> Yes, I'm being optimistic about the userbase but we must agree Fossil
>> to mu
On 13 March 2015 at 05:59, Jan Nijtmans wrote:
> I read in this thread) with Richard's conclusion that work has been lost
> due to fossil, but David Mason should have the final word on that (the
> DELETE's in David's original story meant that those _unchanged_ files
No I copied the script that creates the fossils directly into that
email, and apart from the warning in red, the instructions to students
are unchanged. The odd student might do something different, but most
will have done only and exactly what the instructions say.
../Dave
On 12 March 2015 at 1
1 - 100 of 160 matches
Mail list logo
