Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
On Tue, May 24, 2011 5:21 pm, Steve Havelka wrote: To John, Ramon, and everyone else who's pouncing on Zed about the fossil bug that deleted his code: You guys need to show some humility. Take your lumps, acknowledge the problem from the user, fix the code, and make a better piece of software. Down all other roads lies madness, or at least mediocrity. The bug was fixed - very promptly. They usually are (nothing to do with me). We are entitled to our opinion that Mr Shaw may possibly have overreacted to some extent. While not necessarily including Mr Shaw in the category, I think that people who expect their SCM tool to save them from all possible mistakes are living in a dream world. There is always a way to lose stuff, whatever products you use. The right response to something lost or broken is to stop and think, and be sure you know where you are before reacting. I also think that your demand for humility conveys a more aggressive tone than the message you answered. Eric ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sun, 22 May 2011 06:50:56 -0400 Richard Hipp d...@sqlite.org wrote: [...] Does anybody have any other suggestions on how to prevent the lose of uncommitted work? Maybe not suggestion to prevent losing of uncommitted work, but I'm thinking about using 'stash' in such situation. Perhaps Fossil could do this automatically. Whenever an 'update' would change any locally modified file, Fossil could stash the changes away first and inform the user. That's sort of what fossil undo does. Except it only stores the most recent change. You are suggesting an auto-stash that keeps backups at each change, and stores them in a visible place such as the stash. An interesting idea... Would we purge the auto-stash on a commit? Or just let it grow until the user manually purged it? This looks like Git's reflog functionality [1]. The basic idea of the reflog is that its entries reference commit objects which could otherwise be lost (for instance due to the current branch's HEAD having been forcibly repositioned to point to another commit (hard reset in Git speak)). 1. http://www.kernel.org/pub/software/scm/git/docs/git-reflog.html ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
On Mon, May 23, 2011 2:44 pm, Konstantin Khomoutov wrote: On Sun, 22 May 2011 06:50:56 -0400 Richard Hipp d...@sqlite.org wrote: [...] Does anybody have any other suggestions on how to prevent the lose of uncommitted work? Maybe not suggestion to prevent losing of uncommitted work, but I'm thinking about using 'stash' in such situation. Perhaps Fossil could do this automatically. Whenever an 'update' would change any locally modified file, Fossil could stash the changes away first and inform the user. That's sort of what fossil undo does. Except it only stores the most recent change. You are suggesting an auto-stash that keeps backups at each change, and stores them in a visible place such as the stash. An interesting idea... Would we purge the auto-stash on a commit? Or just let it grow until the user manually purged it? This looks like Git's reflog functionality [1]. The basic idea of the reflog is that its entries reference commit objects which could otherwise be lost (for instance due to the current branch's HEAD having been forcibly repositioned to point to another commit (hard reset in Git speak)). 1. http://www.kernel.org/pub/software/scm/git/docs/git-reflog.html Well, not really. This discussion has been about protecting files in a working directory, whereas the git thing is about unreferenced commits in the repository being protected against garbage collection! Fossil has no such thing as an unreferenced commit and doesn't ever lose anything from the repository unless it is explicitly shunned (which is never part of a normal workflow). Eric ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
A multi-level stash could end up performing the one feature of git I like over fossil: that I can do nonsense commits onto a branch I don't push, then git rebase -i them into beautiful sense before I commit... I've wondered if that should be available as a feature on fossil's private branches (in effect, when the private branch merges, rather than just being one commit, let it be a user-chosen set of commits with the private branch commits split between them as per specification), but it might be more flexible to let people mess with stashes rather than private branch shenanigans. ABS -- Alaric Snell-Pym http://www.snell-pym.org.uk/alaric/ ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
Richard's question regarding a multi level undo, and when to purge, got me thinking; and I apologize for posting mid - thought stream ... What if fossil kept track of all the commands issued that change either the repository or the working files. Obviously, it already does this at some level (commits and merges); in the case of a revert (or even an update), it would save the affected files, perhaps by creating an automatic branch. Fossil now has the files but also the complete command path to reproduce a particular scenario, which would help in debugging. This would really fill any gap in the stated goal of never losing any work; not only committed work, but also work in progress. From: fossil-users-boun...@lists.fossil-scm.org [mailto:fossil-users-boun...@lists.fossil-scm.org] On Behalf Of Richard Hipp Sent: Sunday, May 22, 2011 5:51 AM To: fossil-users@lists.fossil-scm.org Subject: Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE! On Sun, May 22, 2011 at 12:04 AM, chi ml-fos...@qiao.in-berlin.de wrote: Ron Wilson schrieb: On Sat, May 21, 2011 at 4:29 PM, Gour-Gadadhara Dasa g...@atmarama.net wrote: On Sat, 21 May 2011 14:32:34 -0400 Richard Hipp d...@sqlite.org wrote: Does anybody have any other suggestions on how to prevent the lose of uncommitted work? Maybe not suggestion to prevent losing of uncommitted work, but I'm thinking about using 'stash' in such situation. Perhaps Fossil could do this automatically. Whenever an 'update' would change any locally modified file, Fossil could stash the changes away first and inform the user. That's sort of what fossil undo does. Except it only stores the most recent change. You are suggesting an auto-stash that keeps backups at each change, and stores them in a visible place such as the stash. An interesting idea... Would we purge the auto-stash on a commit? Or just let it grow until the user manually purged it? -- 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
Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 10:20 PM, Ron Wilson ronw.m...@gmail.com wrote: On Sat, May 21, 2011 at 4:29 PM, Gour-Gadadhara Dasa g...@atmarama.net wrote: On Sat, 21 May 2011 14:32:34 -0400 Richard Hipp d...@sqlite.org wrote: Does anybody have any other suggestions on how to prevent the lose of uncommitted work? Maybe not suggestion to prevent losing of uncommitted work, but I'm thinking about using 'stash' in such situation. Doing a fossil update should never delete uncommitted changed files. Zed's post implies this happened. Using Zed's repo, I think I have reconstructed exactly what happened. When he entered fossil update because of bug in the logic that figures out what check-in to update to, it tried to update to no-such-checkin which contains no files. So it dutifully went through and removed all the current check-in files. But: any files that had been edited locally would not have been removed. They would have been flagged as conflicts and left unchanged. So after the malfunctioning update, Zed would have had all his files removed, except for those he had edited. So, even though Fossil malfunctioned, safety mechanisms in Fossil prevented work from being lost. So far... What happened next is less clear. But some additional commands were entered, including fossil update trunk and fossil revert. The exact sequence of commands is unknown to me and probably forgotten by Zed at this point too. But whatever they were, they managed to delete his edits. Note in particular that the revert command is a request for Fossil to delete your edits, so it was doing exactly what it was asked to do. Note further fossil revert can be reversed using fossil undo, in case you happen to revert accidentally. But, unfortunately, there is only one level of fossil undo so if you do something else after the fossil revert, your changes are lost permanently. To be clear: Fossil should not have malfunctioned. Yet even so, no work was lost as a result of the malfunction. The safety mechanisms built into Fossil did their job and uncommitted changes were preserved. The work was lost when Zed panicked and started entering a bunch of additional commands, in an attempt to recover, without stopping to think through what was happening. In fairness to Zed, I might well have done the same thing. That said. I routinely backup my projects so I am far less likely to loose more than a day's work. This is not a matter of not trusting a given VCS, whether Fossil, git, some expensive commercial VCS or any other, it is simply a matter of prudence. Better to have multiple backup systems as this helps mitigate the effects of failures in any one system. I've never lost uncommitted work due to Fossil, in four years of heavy use. But I have certainly lost work due to an ill-conceived rm or cp. More than once I have done an rm with some wildcard in the argument, only to realize, milliseconds after pressing Enter, that I had just trashed everything I had done so far that day. It's a bad feeling. -- 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
Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
On May 22, 2011, at 04:20 , Ron Wilson wrote: Doing a fossil update should never delete uncommitted changed files. Zed's post implies this happened. No, his post states that he killed his uncommitted work with fossil revert. And due to earlier errors fossil undo didn't help. Kind regards, Remigiusz Modrzejewski ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
Richard Hipp schrieb: (...) Does anybody have any other suggestions on how to prevent the lose of uncommitted work? Maybe not suggestion to prevent losing of uncommitted work, but I'm thinking about using 'stash' in such situation. Perhaps Fossil could do this automatically. Whenever an 'update' would change any locally modified file, Fossil could stash the changes away first and inform the user. That's sort of what fossil undo does. Except it only stores the most recent change. You are suggesting an auto-stash that keeps backups at each change, and stores them in a visible place such as the stash. An interesting idea... But only if an update would modify local uncommitted changes, I think. So if I commit every time before I update, no auto-stash would be necessary. Would we purge the auto-stash on a commit? Or just let it grow until the user manually purged it? No, I feel it should not purge the auto-stash on commit. It would be safer, if it has to be deleted manually. Then I have explicitely to choose that I do not those changes anymore. Fossil cannot know my intentions. And tracking all of my actions to be sure that the auto-stashed changes were really re-introduced into my working copy would be a ehrm tricky task to implement. What Fossil could do is to warn on every commit I do until those auto-stashes are dropped again (perhaps with asking for permission to proceed with current checkin in face of auto-stashes). Ciao, chi :-) ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
You have no trunk. I can reproduce what you saw by cloning mongrel, opening it, then doing the update. If you have no trunk you probably want to add the branch you want to your open fossil open ../mongrel.fossil ws-hybi-7 The fix in fossil would be to have a real branch selected on open if one is not specified. I.e. default to trunk but if trunk does not exist default to something that does. Hopefully my analysis is accurate :) On Sat, May 21, 2011 at 8:55 AM, Zed A. Shaw zeds...@zedshaw.com wrote: I don't know what the hell has been changing lately, but this is really starting to piss me off. First I get tons of leaves that won't go away and that I have to constantly close over and over, and *now* I'm getting this crap: http://dpaste.de/cY4y/ I can put up with the stupid leaves behavior, but this is completely unforgivable. There's no way in hell *anyone* should be able to get fossil in a state that causes it to REMOVE ALL MY FILES. How do I fix this, and more importantly, how is it going to be prevented in the future? And no, nobody on my project actually did this. There's no commit that removes everything, and in fact fossil itself thinks the files are missing after the update. -- Zed A. Shaw http://zedshaw.com/ ___ 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
Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 09:29:33AM -0700, Matt Welland wrote: You have no trunk. I can reproduce what you saw by cloning mongrel, opening it, then doing the update. If you have no trunk you probably want to add the branch you want to your open fossil open ../mongrel.fossil ws-hybi-7 There is a trunk, I'm doing updates from trunk and it's had trunk for a *year*. It had trunk last night before that branch. Also, if there was no trunk, then why would it update the branch, think there's nothing in it, remove all the files, then say they're missing? That's not it. -- Zed A. Shaw http://zedshaw.com/ ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
One correction, you do have a trunk but fossil is not recognizing it: fossil branch /tmp/mongrel proxymustdie * ws-hybi-7 That looks like a fossil bug to me since trunk is not marked as closed as far as I can tell. On Sat, May 21, 2011 at 9:29 AM, Matt Welland estifo...@gmail.com wrote: You have no trunk. I can reproduce what you saw by cloning mongrel, opening it, then doing the update. If you have no trunk you probably want to add the branch you want to your open fossil open ../mongrel.fossil ws-hybi-7 The fix in fossil would be to have a real branch selected on open if one is not specified. I.e. default to trunk but if trunk does not exist default to something that does. Hopefully my analysis is accurate :) On Sat, May 21, 2011 at 8:55 AM, Zed A. Shaw zeds...@zedshaw.com wrote: I don't know what the hell has been changing lately, but this is really starting to piss me off. First I get tons of leaves that won't go away and that I have to constantly close over and over, and *now* I'm getting this crap: http://dpaste.de/cY4y/ I can put up with the stupid leaves behavior, but this is completely unforgivable. There's no way in hell *anyone* should be able to get fossil in a state that causes it to REMOVE ALL MY FILES. How do I fix this, and more importantly, how is it going to be prevented in the future? And no, nobody on my project actually did this. There's no commit that removes everything, and in fact fossil itself thinks the files are missing after the update. -- Zed A. Shaw http://zedshaw.com/ ___ 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
Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 09:33:56AM -0700, Matt Welland wrote: One correction, you do have a trunk but fossil is not recognizing it: fossil branch /tmp/mongrel proxymustdie * ws-hybi-7 Yep, I see that now, but that doesn't explain why it would *REMOVE ALL THE FILES AND THEN THINK THEY ARE MISSING!* Not yelling at you, it's just about the dumbest thing I've ever seen. -- Zed A. Shaw http://zedshaw.com/ ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 11:55 AM, Zed A. Shaw zeds...@zedshaw.com wrote: I don't know what the hell has been changing lately, but this is really starting to piss me off. First I get tons of leaves that won't go away and that I have to constantly close over and over, and *now* I'm getting this crap: http://dpaste.de/cY4y/ I can put up with the stupid leaves behavior, but this is completely unforgivable. There's no way in hell *anyone* should be able to get fossil in a state that causes it to REMOVE ALL MY FILES. (1) fossil undo should restore all your files whenever something like this happens. (2) I just checked in a change that prints a panic message if Fossil gets into a state where it might want to delete all your files on an update. Still searching for the root cause of the problem How do I fix this, and more importantly, how is it going to be prevented in the future? And no, nobody on my project actually did this. There's no commit that removes everything, and in fact fossil itself thinks the files are missing after the update. -- Zed A. Shaw http://zedshaw.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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
Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 12:46:56PM -0400, Richard Hipp wrote: (1) fossil undo should restore all your files whenever something like this happens. (2) I just checked in a change that prints a panic message if Fossil gets into a state where it might want to delete all your files on an update. Still searching for the root cause of the problem That doesn't matter. This repo is now so totally hosed nobody can use it. I tried upgrading to the latest fossil just to see if that might fix it, and no, now I can't login. Autosync fails, even after I reset my password. So now I've got a repo with a missing trunk, a commit that erases all my code, and nobody can log into it. And all anyone did was make a branch. It's not like we're using it weird or anything. We hardly ever branch, I'm the main committer, nobody does anything fancy with it. Based on this, I can't keep using fossil. Bad leaves floating around, erasing commits, broken logins, complex sql to remove a spam ticket, and it now cost me 3 days of work. I hate to say it, since I love the design so much, but this is the end of fossil for me. Thanks for making it awesome for a year or so. -- Zed A. Shaw http://zedshaw.com/ ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 12:46 PM, Richard Hipp d...@sqlite.org wrote: On Sat, May 21, 2011 at 11:55 AM, Zed A. Shaw zeds...@zedshaw.com wrote: I don't know what the hell has been changing lately, but this is really starting to piss me off. First I get tons of leaves that won't go away and that I have to constantly close over and over, and *now* I'm getting this crap: http://dpaste.de/cY4y/ I can put up with the stupid leaves behavior, but this is completely unforgivable. There's no way in hell *anyone* should be able to get fossil in a state that causes it to REMOVE ALL MY FILES. (1) fossil undo should restore all your files whenever something like this happens. (2) I just checked in a change that prints a panic message if Fossil gets into a state where it might want to delete all your files on an update. Still searching for the root cause of the problem How do I fix this, and more importantly, how is it going to be prevented in the future? Problem fixed in the latest fossil checkin. The issue was this: You were at the tip of trunk but there is another branch (ws-hybi-7) that starts at trunk. When you said fossil update without given an argument of what to update to, fossil tried to find the latest check-in in the current branch to update to. This computation failed due to the ws-hybi-7 branch, and so it tried to update to nothing. All of your files should have been preserved. fossil revert or fossil undo or fossil update trunk should have restored everything. Even files in your checkout that had been edited should have been preserved. If not, that is a totally different problem - please report it separately. And no, nobody on my project actually did this. There's no commit that removes everything, and in fact fossil itself thinks the files are missing after the update. -- Zed A. Shaw http://zedshaw.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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
Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 12:57 PM, Zed A. Shaw zeds...@zedshaw.com wrote: On Sat, May 21, 2011 at 12:46:56PM -0400, Richard Hipp wrote: (1) fossil undo should restore all your files whenever something like this happens. (2) I just checked in a change that prints a panic message if Fossil gets into a state where it might want to delete all your files on an update. Still searching for the root cause of the problem That doesn't matter. This repo is now so totally hosed nobody can use it. I tried upgrading to the latest fossil just to see if that might fix it, and no, now I can't login. Autosync fails, even after I reset my password. So now I've got a repo with a missing trunk, a commit that erases all my code, and nobody can log into it. I just cloned your repo. Everything is working fine. Breath, Zed. And all anyone did was make a branch. It's not like we're using it weird or anything. We hardly ever branch, I'm the main committer, nobody does anything fancy with it. Based on this, I can't keep using fossil. Bad leaves floating around, erasing commits, broken logins, complex sql to remove a spam ticket, and it now cost me 3 days of work. I hate to say it, since I love the design so much, but this is the end of fossil for me. Thanks for making it awesome for a year or so. -- Zed A. Shaw http://zedshaw.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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
Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 01:02:19PM -0400, Richard Hipp wrote: Problem fixed in the latest fossil checkin. Sorry, but I can't have this happen again. It already cost me 3 days of work and erased all my files. There's no way I'm going to use a VCS that erases all my files no matter how good it is. As much as I hate git, at least I know it'll keep working. Thanks for the great design of the software and all your help while I used it. -- Zed A. Shaw http://zedshaw.com/ ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
Do not worry Shaw, we shall manage to survive without you. err... how much did you contribute to the project? RR 2011/5/21 Zed A. Shaw zeds...@zedshaw.com: On Sat, May 21, 2011 at 01:02:19PM -0400, Richard Hipp wrote: Problem fixed in the latest fossil checkin. Sorry, but I can't have this happen again. It already cost me 3 days of work and erased all my files. There's no way I'm going to use a VCS that erases all my files no matter how good it is. As much as I hate git, at least I know it'll keep working. Thanks for the great design of the software and all your help while I used it. -- Zed A. Shaw http://zedshaw.com/ ___ 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
Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 1:40 PM, Zed A. Shaw zeds...@zedshaw.com wrote: On Sat, May 21, 2011 at 01:02:19PM -0400, Richard Hipp wrote: Problem fixed in the latest fossil checkin. Sorry, but I can't have this happen again. It already cost me 3 days of work and erased all my files. There's no way I'm going to use a VCS that erases all my files no matter how good it is. As much as I hate git, at least I know it'll keep working. fossil export | git fast-import will get your stuff moved over efficiently. Thanks for hanging out with us. I expect you might come back to fossil someday, and if you do you will be welcomed. Thanks for the great design of the software and all your help while I used it. -- Zed A. Shaw http://zedshaw.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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
Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sun, May 22, 2011 at 1:44 AM, Ramon Ribó ram...@compassis.com wrote: Do not worry Shaw, we shall manage to survive without you. err... how much did you contribute to the project? While I shouldn't feed the troll, I can't help but point out Zed's blog posts and peepcode video convinced me to give fossil a try. I hadn't heard of fossil before. I'm sure I'm not the only one. Thanks Zed. Ambrose ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 1:57 PM, Matt Welland estifo...@gmail.com wrote: Hi Zed, Please confirm if you really lost local changes. That would be a big concern for me. I haven't lost any non-checked in work and would like to keep it that way. I agree with Matt. I'm thinking you didn't really lose any work - the update bug just took you off into nah-nah land, from which you could easily recover using fossil update trunk, fossil undo, or fossil revert. If you did lose uncommitted changes, that is indeed a problem that needs to be worked on, but I don't see how that would be possible, even with the bug you hit. The 3-days of work seems to be an exaggeration as well, seeing as you checked into trunk just yesterday. Please, Zed, tell us what really happened. And just to confirm, nobody is thinking that any checked-in change have every been lost, right? No tool is perfect and if there is a bug in fossil that causes local changes to be inadvertently discarded we'd all like to know about it so it can be fixed. Thanks! Matt -=- On Sat, May 21, 2011 at 10:40 AM, Zed A. Shaw zeds...@zedshaw.com wrote: On Sat, May 21, 2011 at 01:02:19PM -0400, Richard Hipp wrote: Problem fixed in the latest fossil checkin. Sorry, but I can't have this happen again. It already cost me 3 days of work and erased all my files. There's no way I'm going to use a VCS that erases all my files no matter how good it is. As much as I hate git, at least I know it'll keep working. Thanks for the great design of the software and all your help while I used it. -- Zed A. Shaw http://zedshaw.com/ ___ 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 -- 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
Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 07:44:40PM +0200, Ramon Ribó wrote: Do not worry Shaw, we shall manage to survive without you. err... how much did you contribute to the project? I ton of new users and notoriety. I think without me pimping fossil and writing about it you guys would still be used by the four guys working on it. But hey, it's good to know that there's so many people working on the project making awesome bugs like this and expecting me to have the time to fix it. You rock! -- Zed A. Shaw http://zedshaw.com/ ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 01:46:49PM -0400, Richard Hipp wrote: As much as I hate git, at least I know it'll keep working. fossil export | git fast-import will get your stuff moved over efficiently. Thanks for hanging out with us. I expect you might come back to fossil someday, and if you do you will be welcomed. Yep, that feature is awesome. :-) And yes, I think if it you come to me and say it's all stable now then I'd easily give it a try, but I have to be practical and get shit done. In other words, it's nothing personal, just business. -- Zed A. Shaw http://zedshaw.com/ ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
Ambrose, I am not a troll. I was just remarking ironically that, although the poster has all the right to use whatever VCS he prefers and that he has all the right to inform all of us of his problems and preferences maybe he should refrain on using this aggressive tone. Nobody likes to loose 3 days work but it is not fair to accusse a free software development community for this. RR 2011/5/21 Ambrose Bonnaire-Sergeant abonnaireserge...@gmail.com: On Sun, May 22, 2011 at 1:44 AM, Ramon Ribó ram...@compassis.com wrote: Do not worry Shaw, we shall manage to survive without you. err... how much did you contribute to the project? While I shouldn't feed the troll, I can't help but point out Zed's blog posts and peepcode video convinced me to give fossil a try. I hadn't heard of fossil before. I'm sure I'm not the only one. Thanks Zed. Ambrose ___ 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
Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 02:05:30PM -0400, Richard Hipp wrote: On Sat, May 21, 2011 at 1:57 PM, Matt Welland estifo...@gmail.com wrote: Hi Zed, Please confirm if you really lost local changes. That would be a big concern for me. I haven't lost any non-checked in work and would like to keep it that way. I agree with Matt. I'm thinking you didn't really lose any work - the update bug just took you off into nah-nah land, from which you could easily recover using fossil update trunk, fossil undo, or fossil revert. If you did lose uncommitted changes, that is indeed a problem that * fossil update trunk --- Nope, this just pretended like it'd already done that. Then status said the files were MISSING. * fossil undo -- Nope, it thought it was in a good state. Basically, the removes happened, but then after that fossil thought *I* removed the files. * fossil revert -- This is what destroyed my work. They were uncommitted changes, so once I did this they were gone. I didn't realize it'd nuke them until it was too late. So nope, this really did screw me over big time. -- Zed A. Shaw http://zedshaw.com/ ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 08:15:37PM +0200, Ramon Ribó wrote: Ambrose, I am not a troll. I was just remarking ironically that, although the poster has all the right to use whatever VCS he prefers and that he has all the right to inform all of us of his problems and preferences maybe he should refrain on using this aggressive tone. Nobody likes to loose 3 days work but it is not fair to accusse a free software development community for this. Yes, it is fair to acuse a project of this. *I* don't put out projects that destroy people's work, and if I do I apologize profusely and work my ass off to fix it. I also have extensive unit tests, frequent notifications of pending features or changes, and awesome documentation that explains how to do everything. Telling me that I should just STFU and fix it yourself when I didn't break it and the project just nuked my code is about the most callous obnoxious thing you could ever say to someone. -- Zed A. Shaw http://zedshaw.com/ ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 2:15 PM, Zed A. Shaw zeds...@zedshaw.com wrote: On Sat, May 21, 2011 at 02:05:30PM -0400, Richard Hipp wrote: On Sat, May 21, 2011 at 1:57 PM, Matt Welland estifo...@gmail.com wrote: Hi Zed, Please confirm if you really lost local changes. That would be a big concern for me. I haven't lost any non-checked in work and would like to keep it that way. I agree with Matt. I'm thinking you didn't really lose any work - the update bug just took you off into nah-nah land, from which you could easily recover using fossil update trunk, fossil undo, or fossil revert. If you did lose uncommitted changes, that is indeed a problem that * fossil update trunk --- Nope, this just pretended like it'd already done that. Then status said the files were MISSING. * fossil undo -- Nope, it thought it was in a good state. Basically, the removes happened, but then after that fossil thought *I* removed the files. * fossil revert -- This is what destroyed my work. They were uncommitted changes, so once I did this they were gone. I didn't realize it'd nuke them until it was too late. So nope, this really did screw me over big time. Bummer. I'm sorry you lost work. The bug that you hit had been there for ages - it wasn't new. But it was obscure. You were just the first to stumble over it. Sorry. If you had done fossil undo immediately, that should have worked. I guess the fossil revert overwrote the undo stack. Maybe to prevent this, I should implement a multi-level undo? Does anybody have any other suggestions on how to prevent the lose of uncommitted work? In any event, the bug is fixed now. Thanks for your advocacy, Zed. You are welcomed back anytime. -- Zed A. Shaw http://zedshaw.com/ ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- 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
Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 11:13 AM, Zed A. Shaw zeds...@zedshaw.com wrote: On Sat, May 21, 2011 at 10:57:45AM -0700, Matt Welland wrote: Hi Zed, Please confirm if you really lost local changes. That would be a big concern for me. I haven't lost any non-checked in work and would like to keep it that way. Oh it's confirmed. That's a major bummer. I couldn't reproduce what you described but see in your latest message that it was the revert that killed your work. I modified a file and did the update and saw this: . REMOVE tools/m2sh/tests/runtests.sh REMOVE tools/m2sh/tests/sample.conf -- WARNING: 1 merge conflicts - see messages above for details. fossil undo is available to undo changes to the working checkout. I actually don't think there is anything we want to change in fossil with respect to this (other than the bug fix already implemented). Losing three days is something you could have (obviously) avoided by checking in more often or by checking in to a private branch. Based on my experience you will want to adopt this behavior with git also. I lost work on git when trying to adapt it to a pre-existing methodology, merging into a modified branch in git is very confusing (at least for me). It wasn't git's fault that I lost the data but it sure was frustrating. -- Zed A. Shaw http://zedshaw.com/ ___ 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
Re: [fossil-users] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, 21 May 2011 14:32:34 -0400 Richard Hipp d...@sqlite.org wrote: Bummer. I'm sorry you lost work. I'm also sorry that Zed has lost work. :-( The bug that you hit had been there for ages - it wasn't new. But it was obscure. You were just the first to stumble over it. Sorry. Despite of that, I'll stay with Fossil knowing well that using some obscure tool like Git, it would happen much often via shooting my own feet. Does anybody have any other suggestions on how to prevent the lose of uncommitted work? Maybe not suggestion to prevent losing of uncommitted work, but I'm thinking about using 'stash' in such situation. What do you think? Sincerely, Gour -- “In the material world, conceptions of good and bad are all mental speculations…” (Sri Caitanya Mahaprabhu) http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810 signature.asc Description: PGP signature ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 02:32:34PM -0400, Richard Hipp wrote: the fossil revert overwrote the undo stack. Maybe to prevent this, I should implement a multi-level undo? Does anybody have any other suggestions on how to prevent the lose of uncommitted work? I've lost sometimes work with this issue, specially when there were few messages telling about conflicts and things like that. I'm not going to implement a multi-level undo, but I'd enjoy it a lot! Thank you, Lluís. ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
On Sat, May 21, 2011 at 4:29 PM, Gour-Gadadhara Dasa g...@atmarama.net wrote: On Sat, 21 May 2011 14:32:34 -0400 Richard Hipp d...@sqlite.org wrote: Does anybody have any other suggestions on how to prevent the lose of uncommitted work? Maybe not suggestion to prevent losing of uncommitted work, but I'm thinking about using 'stash' in such situation. Doing a fossil update should never delete uncommitted changed files. Zed's post implies this happened. That said. I routinely backup my projects so I am far less likely to loose more than a day's work. This is not a matter of not trusting a given VCS, whether Fossil, git, some expensive commercial VCS or any other, it is simply a matter of prudence. Better to have multiple backup systems as this helps mitigate the effects of failures in any one system. ___ 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] WHY IS FOSSIL REMOVING ALL MY CODE!
Ron Wilson schrieb: On Sat, May 21, 2011 at 4:29 PM, Gour-Gadadhara Dasa g...@atmarama.net wrote: On Sat, 21 May 2011 14:32:34 -0400 Richard Hipp d...@sqlite.org wrote: Does anybody have any other suggestions on how to prevent the lose of uncommitted work? Maybe not suggestion to prevent losing of uncommitted work, but I'm thinking about using 'stash' in such situation. Perhaps Fossil could do this automatically. Whenever an 'update' would change any locally modified file, Fossil could stash the changes away first and inform the user. That way one could apply the stash to the updated working tree dealing with conflicts and such. After all went well the stash may be dropped manually. Then it would be much more difficult to lose local modifcation not committed so far. Doing a fossil update should never delete uncommitted changed files. Zed's post implies this happened. The 'stash first' should protect us here too :-) (...) Just my two cent ... Ciao, chi :-) ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
