I thought it was, too, but with no hash who can be sure?
I cannot say that I have found hash a guarantor of certainty.
Of course there would have to be that one character who leaves crappy commit messages. "Made some changes."
Special appeal for legal philosophy buffs, too.
6 is great, but I believe the judges would also have accepted "a novel by Vivian Darcsbloom".
So now we know* which objective facts nosflow is referring to when he uses "morning" and "excitably".
*To be fair**--although that was most certainly not my intention in writing this comment--he may have described it excitedly yesterday morning by some other means than a front-page post on this blog.
**And of course we actually only really know his stated intention to do so from the 11-302-12 12:12 AM comment. But I would expect an interlocutor as careful as neb to have explained any deviations from that stated intention so as to not confuse the careful and interested reader of his word.
Alternately, you know that I don't always follow through on my stated intentions.
I don't have any opinions on experimental literature, but I've developed a pet peeve about commit logs that neb might appreciate... I always phrase commit messages in the third person present tense, e.g., "Changes the fizz to buzz". This has the "nice" property that you can interpolate "Commit X" nicely, e.g., "[Commit X] changes the fizz to buzz." It annoys me when people use the second person/imperative, e.g., "Change the fizz to buzz." Who should change it? When will it change? (This is a particularly stupid thing to get annoyed by because the latter style is by far the most common.)
"Change the fizz to buzz" should be the bug/issue/task title. Perhaps that's just getting copied into the commit logs?
"Changes the fizz the buzz" means "drinks a beer".
Another thing that annoys me is Perforce. And another thing that annoys me is rebasing.
When your code's on fire and you're running down the street, people will get out of your way.
Yawnoc's siding with the flat-affect prose style.
I wonder what Yawnoc think about any of this?
I've been trying to figure out what a commit message is just by looking at the output of this generator. I'm not having much luck.
22:
Committing in accordance with the prophecy.
22: Whoever wrote that is way too amused by the word "derp".
22 - yeah, that site really gives NO clue at all. Still a foreign word to me.
this doesn't help that much either. I'm getting the sense that these are messages you submit when you make changes to software as a part of a shared project. Is it a "commit" message because the group is now "committed" to a change?
27.2, yes; 27.3, I'd have said the change was committed to the group (written into the shared repository we all copy onto our working machines and progress from), but good enough.
The group isn't as committed to the change because one point of change-trackers is that we can say 'Undo change 0x33d37 but not the later ones, insofar as that's possible' when it turns out that 0x33d37 was a bad idea.
I'd have said the change was committed to the group
Wouldn't "submitted" be more natural English?
20% more mauve.
New and improved?
You gotta know when to hold 'em.
Yawnoc will hate me, but apparently the plurality of my commit messages are written in the present progressive with the "this commit is" elided. Lots of "fooing the bar quux" and "distimming gostak-resistant doshes" and "sleeping furiously to fix broken build".
There are more complicated systems in which proposed changes are submitted to agents who can choose whether to commit them to a particular repository.
Wouldn't "submitted" be more natural English?
No (it isn't submitted for their approval or disapproval), but I also wouldn't say what clew said.
32 to 29. While I'm here, let me recommend Ellen Ullman's _The Bug_.
Wouldn't "submitted" be more natural English?
Think "committed" as in "to a mental institution".
You don't know they're in the present, with the copula omitted. (Why not "This comment was fooing the bar quux" or "This comment has been distimming gostak-resistant doshes" or "This comment will be sleeping furiously to fix broken build"?) Perhaps best just to construe them as gerunds and leave it at that.
29, 32 - I believe the term was adapted from relational databases that support making a series of changes (a transaction) then either committing the transaction or rolling back to a previous savepoint.
Think "committed" as in "to a mental institution".
Yes, the change is being committed to the repository. You dink around with it on your computer and then check a version in, as it were, by committing it.
And also Ullman's _Close to the Machine_. I haven't read _By Blood_ because it looks so dispiriting.
"Committed" and "commit message" are vocabulary particular to a certain strain of revision control systems; other systems do in fact use "submitted" for basically the same operation. In perforce, for example, you "submit" a "changelist" with a "description" rather than committing a whatever with a commit message.
40: Useful.
I was hoping for extra nifty Mercurial terminology, but haven't found any.
Mercurial is pretty strongly influenced by git, though, isn't it? I'd imagine darcs, arch, or Monotone would be a better place to see weird computer scientist terminology bubbling to the surface.
This thread prompted me to go see if PANVALET, the source code repository I used in the 70's, was still remembered, and it is apparently still in use! Owned now by Beelzebub Computer Associates.
44.last: HA. CA in action when they bought Pansophic (who developed PANVALET).
Computer Associates International Inc., true to its reputation for lowering the boom quickly following an acquisition, is cutting Pansophic Systems Inc.`s work force by 500 to 600 people, or as much as 38 percent.
Mine are past tense sentence fragments with the subject omitted, but I think I'll start doing them Yawnoc-style.
David Roundy: At its most basic level, the theory of patches is about the commutation, or reordering, of changes in such a way that their meaning doesn't change. The rules of commutation tell us when, for example, one patch requires another, since dependent patches cannot be commuted. Once the commutation primitives have been worked out, one can do all sorts of interesting (and useful) operations, such as merging. And such operations can be shown to be independent of order, i.e. it doesn't matter whether you merge patch A or patch B first, you'll get the same result.
How to use this in the novel?
With this (about GSMorson's work)?
At its heart, _The Words of Others_ is a case for the quotation as a literary form: a self-enclosed unit of thought that identifies itself, as such, independent of context.
So is this what the East Bay meetup was like?
I believe mercurial and git were initially developed concurrently.
48: I was thinking about "sideshadowing".
How the fuck can apt experience errors installing OpenSSL on a fresh system?
mercurial came before git, then was something else.
committing a whatever with a commit message.
The git jargon is "committing a changeset" but I'd also accept "committing a commit."
So is this what the East Bay meetup was like?
Add coq jokes and beer, and then yes.
and then yes
So a prog meetup! Nice.
Is there any way to discourage the github culture of "hey this worked once on my machine so I'm going to put it up on github with no documentation because that will be totally useful to others"?
||
Print your own sex toys! Pretty interesting, although I think (and the caveats toward the end kind of imply) there's less here that's both novel and meaningful than some of the people involved would like you to think.
|>
Is there any way to discourage the github culture of "hey this worked once on my machine so I'm going to put it up on github with no documentation because that will be totally useful to others"?
Don't use that stuff?
I really should learn to use git in addition to joking about it.
While I'm here, let me recommend Ellen Ullman's _The Bug_.
Oh, hey, I just read that in August, after it had been sitting on my shelf for years. I would also recommend it, though I didn't think it was as good as Close To The Machine and would warn that it's a bit depressing.
I'm a fan of Ellen Ullman's writing. In college I was doing a paper which touched on "computer culture" and her essay in Wired Women was by far the best written thing that I came across in my reading.
I feel like I should also recommend Pat Cadigan at this point, but perhaps I have mentioned her enough on this blog that it is unnecessary. I do think Synners is my favorite cyberpunk novel, despite the weak ending.
63. I was doing that already; it didn't work.
Did you document what you were doing so we can try it ourselves?
62: Consider the sex toys of the 3D printer -- they toil not, neither do they spin. Yet Solomon in all his glory was not arrayed such as these.
I never did persuade anyone to do all the hard work in sp0rkvοlution. 'Course, all I have is the bloviating, not even code-once.
You be the *.
One of the two profitable enterprises I know of in the hackerspace nearest me is sex toys. I'm so happy I'm a beta.
All I know is, the Betta fish always make me sad at the pet store. So lonely.
67: Step 1: Ignore crap github culture
Step 2: Want badly to send realtime MIDI events from Python, preferably in a cross-platform way, but willing to do so Mac-only
Step 3: Google 'python midi wrapper' and several variations thereon
Step 4: Find promising-looking python wrappers around PortMIDI hosted on github
Step 5: FUCKING DEPENDENCIES
Step 6: Segfault
Step 7: It's actually easier to run fucking VMWare and develop this project by running it in a virtual Windows machine
Step 8: Whine to the Mineshaft about it
73: take it up with SE Hinton, Stanley.
Not VHS, Von Wafer. VHS is said to have won the videotape format wars by allowing porn. See also Brave New World, because I know this is a high tone lit'ry crowd.
"With Pyknon you can generate Midi files quickly and reason about musical proprieties."
Probably a typo, but hope springs eternal.
62: I kinda feel that we already can do those things in a better way at this point. Possibly in five years time 3d printing will be competing with casting, but right now doesn't seem super compelling to me.
79: at least some of them are just doing prototyping with 3-d printing, which probably makes more sense.
NaCoMeNoMo has passed again and I hardly dipped a quill in ink, I'll confess.
62.Charlie Stross is waaayyy ahead of you.
What three qualities doth prototyping chiefly require?
Has anyone made the "chewing beta nut" joke? If not, I'd like to reserve the area for further exploitation development.
Is that like "sucking hind teat"?
It's like someone just built the tower of babel.
I begged you not to break the blog text.
It was never very good, but I do well at driving ranges.
I guess I could post something.
I did just go grocery shopping. I could complain.
will you give me a back rub? maybe I should start posting as unf.
61: Things on github are supposed to be useful to other people? I'm always surprised when someone stars or forks one of my repos. I have public stuff up because it's cheaper than tarsnap and you're only allowed a limited number of private repos.
I have a couple of substantial projects up there, and the README pretty much says "I'm putting this here because, well, why not? If you want to get this working you'll have to deal with X and Y, which are pretty annoying".
you're only allowed a limited number of private repos.
Why not switch to bitbucket, then?
I was under the impression that bitbucket is mercurial only, but, apparently, that's no longer true (if it ever was).
Now, I suppose my only reason is inertia. Since some folks are forking or following what I'm doing, I don't want to switch and inconvenience them unless there's a real benefit for me. If bitbucket supported darcs, so that I could have all my old unconverted repos in the same place as my current stuff, I'd probably switch.
There are fans of The Quincunx? I'm having a hard time correlating those folks with fans of Pale Fire
97 - There are! A lot of them used to endlessly parse on my website.
I do like the idea of a novel built out of engineering change requests, not even necessarily commits, could be hardware. Like William Golding's "The Spire", but for software, 747s, ships etc.