Warren, thanks for your reply. It was pretty comprehensive, and I liked it, even when those are bad news. I actually discovered some of them myself a long time ago... Same goes to GIT, That's the reason I've only toyed with the idea, but then started to think about the many many things that have to be done to create the "illusion". The original email was meant to ask if someone had thoughts about it.
The shim wouldn't be meant for regular users, but mostly for GUI text editing suites, that don't go over the entire combinations that a crazily imaginative command line user could make. Those tools basically allow you to commit, select which files and type in a comment, move inside the branches, and pretty much that. Actually I don't even think the behaviour should be the exact same one from git. Perhaps it could actually allow some differences. After all, I do want to use fossil in the first place, not git... Perhaps it should return warns when there is a known behaviour difference. Is kinda what you do when you use Openoffice to edit Word documents, Word to edit ... wordperfect (yeah, I think Microsoft golden years are gone... Embrace, extend and extinguish... what an era), or Apple Pages to edit Word. You know that you're doing an imperfect thing, that the result won't be perfect, yet you continue to use it, and even learn the differences. The programs warn you that the things you are willing to save could not be compatible, yet you proceed to save them. To put it back again in better words, the idea is to make an adaptor that let's existing apps (mostly IDEs) to use Fossil as another version control system, until they get a native plugin, but via using the existing GIT tool interface. This email was meant to start a conversation about that. So this note is to say that I love, really, love the idea of discussing usefulness of staging or not (my personal opinion is that is not useful), but mostly the idea of select which lines to keep for a specific commit. I will then proceed to open another discussion about that, sort to keep this one for the "shim" idea. Anyone who thinks a shim can at least be an idea to try? Also, ideas from IDEs users are welcomed (as I personally don't know them all, mostly, I don't use them often, I edit with nano and nowadays with gedit, unless on Windows, where I use notepad++ and Microsoft Visual C 6). On Fri, Mar 20, 2015 at 5:54 AM, Ramon Ribó <ram...@compassis.com> wrote: > A possible workflow to do partial commits in fossil could be: > > - fossil diff --tk --partial-commit > > (A special version of fossil diff --tk appears where there is a > checkbox in every difference) > > - Select some differences > > - Save and quit > > (Then, an automatic "fossil stash" is performed where the original > modified files are stored. The files left in the working area only > contain the selected differences) > > - Compile and test > > - fossil commit > > (command could print a message remembering us that there is a > pending automatic stash and the way to recover it) > > - fossil stash pop > > > The trick here is that the GUI tool should perform the stash > automatically, to avoid accidental loss of modified code and should > inform the user of the situation. > > > RR > > > 2015-03-20 9:31 GMT+01:00 Gour <g...@atmarama.net>: > > Richard Hipp <d...@sqlite.org> writes: > > > >> Please help me to understand why people think that the git staging > >> area is a good idea. > > > > Considering that git provides 'commit -a' option which practically > > eliminates staging area. > > > > Moreover, the author of very popular Pro Git book > > ( > http://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository > ) > > in "Skipping the Staging Area" section says: > > > > "Although it can be amazingly useful for crafting commits exactly how > > you want them, the staging area is sometimes a bit more complex than you > > need in your workflow. If you want to skip the staging area, Git > > provides a simple shortcut. Adding the -a option to the git commit > > command makes Git automatically stage every file that is already tracked > > before doing the commit, letting you skip the git add part..." > > > > which led me to conclude that we can live in Fossil without it. ;) > > > > > > Sincerely, > > Gour > > > > -- > > Therefore, without being attached to the fruits of activities, > > one should act as a matter of duty, for by working without > > attachment one attains the Supreme. > > > > > > _______________________________________________ > > fossil-users mailing list > > fossil-users@lists.fossil-scm.org > > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
