At the risk of wading in to a minefield, I have some thoughts.....
On Fri, Oct 21, 2016 at 2:14 PM, <fossil-users-requ...@lists.fossil-scm.org>
wrote:
>
> From: Nikita Borodikhin <elit...@gmail.com>
> Date: Fri, 21 Oct 2016 16:02:33 +0000
>
> == combined log - history ananlysis ==
>
> The most unusual thing about Fossil is that it does not have "log" command.
> [...] In Fossil, there is no easy command line way to get the history of a
> subtree.
>
>
Other than:
fossil finfo path/to/dir/*
I don't know what history of a subtree would be. Fossil tracks files, not
directories
I believe that most users are used to that universal log command and I
would be surprised if fossil's timeline/finfo duo is not _the_ most
thing people struggle with in the beginning of their relationship with
Fossil.
>
>
Never bothered me. I rarely use finfo, I suspect this may have been the
case in the early days of Fossil, with finfo being added as a separate
command, perhaps to avoid issues with the parsing of the existing timeline
command.
If someone were inclined enough to implement a new log command that could
show either commit history or file history, the constraints of the existing
timeline command could be avoided.
> == relative revisions - history analysis ==
>
> In Fossil there is no way to refer to a parent of a revision, with the
> exception the parent of checked out revision.
>
>
Once in a while, being able to specify a revision relative to another would
be handy.
While git's ^ suffix is simple, tag+n or tag-n would be more flexible.
== show - history analysis ==
>
> I like "git show" and "svn log --diff" as they give me all information about
> commit I need ...
> It would be even better if show were universal. By "universal" I mean that,
> ideally, it should work the same way for a tree change, file change, wiki,
> ticket and so on.
>
>
I don't really miss this command, as it is very easy to just use the web UI
to see the differences.
But, I can see where a "fossil show" command could be handy as finfo isn't
really a variant of info for files.
== "checkout as repository" ==
>
> When you come from svn or git, the very first question is "why do I need to
> _open_ the repository I've just cloned?". ...
> Each of computers I use has at most one checkout of each repo.
>
>
Coming from SVN, "fossil open" was basically the same as "svn checkout"
with a different name. (I'd prefer "fossil checkout" be an alias of "fossil
open", but in Fossil it has a different function.)
The few times I have setup a local "slave" SVN repository I still had to do
"svn checkout" to create a working copy. (SVN is not a distributed VCS, so
you must commit directly to the one repository. "Slave repositories" were
introduced as a way to have a local, read-only copy of the repository, but
commits still have to go first to the "main" repo, then the slaves have to
pull from the main.)
So doing "fossil open" after doing "fossil clone" (or "fossil new") was
nothing strange or new to me.
Perhaps adding a "--open" option to the "fossil clone" and "fossil new"
commands would be a reasonable enhancement to Fossil. (I think this
approach would be cleaner than having Fossil try to guess what you are
asking it to do.)
"git clone" was weird to me at first. Also I very much used SVN's ability
to have multiple working copies checked out from a single repository. With
git I have to clone the repository to get additional working copies. And
then I have to push/pull changes between them.
== wiki syntax ==
>
> One of the weaknesses of the web interface is wiki syntax. After you chose
> markup format and click "Create", you have to keep formatting rules in mind.
> ... I would appreciate a lot if there were links to the official wiki_rules
> and md_rules files.
>
>
This can be added by editing the header and/or footer (Admin->Skins->Header
or ->Footer). It is possible to conditionally display links based on the
page being displayed (and/or other factors).
Perhaps someone could update the default "skin" for the Fossil UI to
include a wiki help link.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
