On Sat, 14 Mar 2015 10:18:35 +0100, Stephan Beal <sgb...@googlemail.com>
wrote:
On Sat, Mar 14, 2015 at 5:05 AM, Richard Hipp <d...@sqlite.org> wrote:
I tried going to the "network" graph
(https://github.com/mackyle/sqlite/network) which seems similar to the
Fossil timeline graph, only sideways.
I needed to use github only once, fortunately, when I wanted to contribute
a small patch to `asciidoc', so I am really a test case for "how does
github feel to a newbie". answer: awkward, to say the very least. this is
quite different to first time encounter with `fossil'. so one probably
should not look to closely on github on how to improve `fossil'. ;-)
The network is primarily intended to show fork-related relationships.
i.e.
whose fork was created/merged at what point. In a way it's similar to the
branch handling in fossil's timeline. github's workflow encourages using
forks rather than branches (the end effect is similar, since a fork can
be
merged in at any time).
my understanding was that a github "fork" is nothing but a clone and not
"really" part of the original project, no? so it really is not comparable
to a branch (be it `git' or `fossil'), no?
in my (probably naive or wrong) view github seems nothing more than a way
to manage changes in different clones of a project which are "suggested"
for cherry-pick merge into the main repo (plus a lot of eye candy I for
one find distracting rather than helpful). so github as far as I can see
is "only" a metastructure on top of `git' and this functionality might (or
might not) be mimicked as part of `fossil' or via some sort of
`fossilhub'. I see that github is immensely successful so no sense arguing
that something like that seems desirable.
just my 2c (probably explaining the very obvious ;-))
j.
re
Am I wrong to think that clicking through the changes in a project
(not necessarily from the beginning, but from some signification
event, say the most recent release) in chronological order is
something that people might commonly want to do?
It's possibly a case of "not missing what one never had."
Some tools, e.g. Google Code, offer the ability to move forward and
backward through commit numbers. e.g. see the links near the top/right of
this SVN browser:
https://code.google.com/p/v8-juice/source/browse/convert/include/cvv8/XTo.hpp?r=2070
But that's at the file level. It has a timeline-like view, but it's not
nearly as informative as fossil's:
https://code.google.com/p/v8-juice/source/list
(But it's easy enough to find the start of the project there.)
Haven't ever spent enough time in github to notice if/how it does
something
similar.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
