Fluid Dynamics <a2093...@trbvm.com> writes: >> Really, you expect me to create an account and publish every little >> > bit of code I play around with on github? >> >> Publication of code for VCS isn't really necessary. RCS which was >> released in 1982 didn't require it (actually, didn't support it). With >> the advent of DVCS, it's not needed now. >> > > Objection: relevance? The OP specifically suggested github,
You don't have to publish with github either, but then you do have to pay them. > >> Sometimes I write some function or big static map or vector or >> > something out a line at a time, saving every couple of minutes or if I >> > pause for any reason. I'm certainly not about to commit code in such a >> > state to a VCS, let alone publish it where others can see it. >> >> That's what rebasing is for, although I agree it doesn't avoid the >> usefulness of a numbered backup. >> > > I don't even know what "rebasing" is. Rewriting history. The general usage pattern is that you start a feature branch, make 20 attempts to get it working before you get it right. Once it's right, you squash your previous commits down so that just the correct changes get in. In the process, you lose the intermediate history, which is a) good because you have deleted all the junk, so it's easier to read and b) bad because you have lost the history. > I'd much rather not have to either, not when my current workflow is > fine for me just so long as my tools have the courtesy not to threaten > to crash in the middle of a save. How many hours, weeks, or months of > ascending some no-doubt-steep learning curve would be involved in > following your recommendation? > > Would I be able to resume making forward progress on my actual project > by Christmas, or would it be closer to Valentine's Day? That sort of depends on you. But, either way, you'll understand rebasing, and you'll have some mighty tales to tell about the rebase vs merge controversy. I've always found these go down very well at parties or romantic dinners. Phil -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
