wyoung2

23 ms·

151.
by wyoung2 11y ago
> I may not own or be associated with the original repository? Then you're doing federated development, and you should continue to use Git or another tool that supports that style of development as a first-class activity. Many years
152.
by wyoung2 11y ago
> While you shouldn't be working on multiple things, I and most other people I met, end up doing so Fossil solves that with branches. Merging a branch into the trunk is equivalent to what Git calls pushing. The difference is that ev
153.
by wyoung2 11y ago
While I am a fan of chains of small cooperating tools, there is something to be said for a single large tool with a well-integrated feature set. Here are some of the advantages you get when the code repo, bug tracker, and wiki are all part
154.
by wyoung2 11y ago
> Fossil does not support versioning directories. While that is true, what would revision 2 look like? "This new directory is also empty, but more so?" My point is that an empty directory isn't really "versionable,&qu
155.
by wyoung2 11y ago
Rebasing can move whole subtrees around in the repo's history, then publish all those changes back to the repo you cloned from. There is nothing like this in Fossil, on purpose. Fossil's shun operation and private branches are ent
156.
by wyoung2 11y ago
> What is the value in having history be static? Because you can trust it. Rewritable history is like maintaining your business ledger on a whiteboard. > I find that rebase comes in handy as I'm working locally This idea that loc