Re: [fossil-users] Detecting checkout/repo mismatch
Thus said Richard Hipp on Thu, 29 Mar 2018 06:51:45 -0400: > You can't. But in more than a decade of use, this has never come up > before? Is this really a serious problem? Do we need to add new checks > to verify that the _FOSSIL_ file refers to the correct repository? I would say it's a ``nice to have'' as I cannot imagine it happening very often. For this to present an actual problem the repositories would have to have identical filenames and rids would have to at least be somewhat consisent. Fossil did return an error about there being a mismatch: > $ fossil commit -m "test 2" > Could not find a valid check-in for RID 6. Possible checkout/repo mismatch. What are the chances that RID 6 would have actually matched a checkin and that those files would also have been found in the repository? Had the right conditions existed, I supposed the commit would have succeeded? Andy -- TAI64 timestamp: 40005abe4741 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Inconsistency of URL handling in Markdown rendering.
Current workaround - I have converted all of the URLs in the markdown into absolute URLs. That means that the hyperlinks for the README.md document always point to the "trunk" check-in, rather than to the versions of the linked documents that are in the same check-in as the README.md file being viewed. I think that is undesirable. But it is a quick fix. Still seeking a better long-term solution... On 3/30/18, Richard Hipp wrote: > Problem reported here: https://news.ycombinator.com/item?id=16714672 > > For the project in question, the README.md file is intended to be the > homepage and to be displayed using the /doc/VERSION URI. But it also > gets display using the /dir URI and in that case the relative > hyperlinks are not correct. I could make the hyperlinks absolute, but > that would tie them to a particular version. > > One solution is to rearrange the files in the project so that the > homepage is called something other than README.md, then it won't be > displayed automatically as part of /dir. > > But I'm seeking a more general solution for how to handle hyperlinks > in Markdown (or Wiki or HTML) documents that can be displayed using a > variety of URLs. > > -- > D. Richard Hipp > d...@sqlite.org > -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Inconsistency of URL handling in Markdown rendering.
Problem reported here: https://news.ycombinator.com/item?id=16714672 For the project in question, the README.md file is intended to be the homepage and to be displayed using the /doc/VERSION URI. But it also gets display using the /dir URI and in that case the relative hyperlinks are not correct. I could make the hyperlinks absolute, but that would tie them to a particular version. One solution is to rearrange the files in the project so that the homepage is called something other than README.md, then it won't be displayed automatically as part of /dir. But I'm seeking a more general solution for how to handle hyperlinks in Markdown (or Wiki or HTML) documents that can be displayed using a variety of URLs. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
