7 ms·

And here is something to take the garbage quality of Git manpages with some humor https://git-man-page-generator.lokaltog.net/ https://git-man-page-generator.l

And here is something to take the garbage quality of Git manpages with some humor https://git-man-page-generator.lokaltog.net/ https://git-man-page-generator.lokaltog.net/ "git-eliminate-head eliminates all downstream heads for a few forward-ported non-counted downstream indices, and you must log a few histories and run git-pioneer-object --pose-file instead. [...]"

pferde 8y ago
Thank you for this, it made my day. :)
philbarr 8y ago
That's fantastic!
arduinomancer 8y ago
That's hilarious
mrzool 8y ago
Nothing short of sublime. Thanks for sharing.
romwell 8y ago
This is a kind of very specific, targeted, niche comedy, excellently executed. I only use Git casually, and I can't tell how much of that text couldn't make sense in an actual doc; it all looked real enough at a glance. Thank you for sharing, this made my week.
zwieback 8y ago
Love it. I'm sold on git but it often feels like I'm in one of those man pages.
- LyndsySimon 8y ago
  In my experience, it gets better. After a while you know everything you need to not only do your job, but to understand and resolve common issues. After a couple of years you'll be at the point where the only time you have to dig through manpages is when you're trying to do something esoteric or clever.
ppezaris 8y ago
oh my sides.
Groxx 8y ago
Impressively small generator data too, given how realistic it reads: https://github.com/Lokaltog/baba-grammar-git-man-page-generator/blob/develop/grammar.baba https://github.com/Lokaltog/baba-grammar-git-man-page-genera... but maybe that's due to the low bar that it's being compared to.
hyperpallium 8y ago
Good to see tax accountants contributing to open source.
paultopia 8y ago
OMG THIS IS THE REALEST
euske 8y ago
Am I only one who's getting an error on Firefox? Content Security Policy: The page’s settings blocked the loading of a resource at self (“script-src”).
MisterOctober 8y ago
Brilliant, absolutely had me rolling. Most cleverly-executed satire I've seen in a long while. "To parse a staged SKIRT_SUBTREE and blame the working histories, use the command git-purchase-pack --snuggle-muster-branch, as after reapplying subtrees..."
virtualwhys 8y ago
Please note[1] that: > To rev-parse an automatic FLOUNDER_LOG or diff the working subtrees, use the command git-link-submodule --retrieve-wrestle-change. I often overlook this detail when trying to hulk smash some broken change I've made upstream (what the manual entry correctly refers to as RIP_OTHER_TIP). [1] https://git-man-page-generator.lokaltog.net/#81394c8bf3806f9d4c29910baab84314 https://git-man-page-generator.lokaltog.net/#81394c8bf3806f9...
sonnyblarney 8y ago
This is funny, but in reality it's not. Git is one of the most amazing, powerful tools ever conceived, with one of the must byzantine and ridiculously designed 'interfaces' ever conceived. People confuse the raw power of a tech, with how well it can be feasibly used. Sadly, due to the later issues, git will only ever be a shadow of what it could have been. With all due respect to Linus, who'd be the first to admit he's not very good at UI stuff (I mean command line as well)... it's truly a sad thing. This is a major 'problem that needs to be solved' I'm interested to see how it could evolve into something 'better'.
- karmakaze 8y ago
  I don't think the complexity of git's command options is a UI problem. It results from the basis of its operation. We could change some names, add or remove some concepts to how some of the operations are performed, but there are simply a large number of actions to handle many edge cases. A better solution for prose was to always be merging with live multiple collaborator updates. Conflicts are visible in real-time. I can't see something like this would work with code. Hmm interesting... unless we only allow additions and refactorings to working checkpoints.
  - P_I_Staker 8y ago
    Yes, I don't really understand all the people trying to "fix git". Git's fine, though the complexity makes it challenging, especially for new users. However the complexity is a direct result of useful features. "Keeping it simple" is great, except when the complexity is needed. I'm hard pressed to name any features I could do without.
    - sonnyblarney 8y ago
      There are two problems: one of inherent complexity, one of UI. First - the UI is a mess, and that should have been fixed. It would make a big difference. Second - is the inherent complexity. That's a good point, but I feel many things could be hidden or obfuscated. Most poignantly, Git does something that most of us do not need: it was designed to work as a 'completely distributed system', i.e. for open source. Almost none of us do that. 95% of uses cases related to you and I working collaboratively, on a project together. The need to have repos which are essentially totally distinct from one another is a huge source of complexity and it simply doesn't need to exist in most cases. So Git is basically an 'admin level tool' that is commonly used in scenarios for which it wasn't meant to be used, with a confusing interface. It's costing a lot of time and money and headaches, I do believe someone may come along eventually and fix it. This thread is essentially evidence of this - see how many people have difficult teaching what should essentially be a simple thing in most cases. Way too many very smart people still spend too much time clustering around in git.

pferde 8y ago

Thank you for this, it made my day. :)

philbarr 8y ago

That's fantastic!

arduinomancer 8y ago

That's hilarious

mrzool 8y ago

Nothing short of sublime. Thanks for sharing.

romwell 8y ago

This is a kind of very specific, targeted, niche comedy, excellently executed. I only use Git casually, and I can't tell how much of that text couldn't make sense in an actual doc; it all looked real enough at a glance. Thank you for sharing, this made my week.

zwieback 8y ago

Love it. I'm sold on git but it often feels like I'm in one of those man pages.

LyndsySimon 8y ago
In my experience, it gets better. After a while you know everything you need to not only do your job, but to understand and resolve common issues. After a couple of years you'll be at the point where the only time you have to dig through manpages is when you're trying to do something esoteric or clever.

ppezaris 8y ago

oh my sides.

Groxx 8y ago

Impressively small generator data too, given how realistic it reads: https://github.com/Lokaltog/baba-grammar-git-man-page-generator/blob/develop/grammar.baba https://github.com/Lokaltog/baba-grammar-git-man-page-genera... but maybe that's due to the low bar that it's being compared to.

hyperpallium 8y ago

Good to see tax accountants contributing to open source.

paultopia 8y ago

OMG THIS IS THE REALEST

euske 8y ago

Am I only one who's getting an error on Firefox? Content Security Policy: The page’s settings blocked the loading of a resource at self (“script-src”).

MisterOctober 8y ago

Brilliant, absolutely had me rolling. Most cleverly-executed satire I've seen in a long while. "To parse a staged SKIRT_SUBTREE and blame the working histories, use the command git-purchase-pack --snuggle-muster-branch, as after reapplying subtrees..."

virtualwhys 8y ago

Please note[1] that: > To rev-parse an automatic FLOUNDER_LOG or diff the working subtrees, use the command git-link-submodule --retrieve-wrestle-change. I often overlook this detail when trying to hulk smash some broken change I've made upstream (what the manual entry correctly refers to as RIP_OTHER_TIP). [1] https://git-man-page-generator.lokaltog.net/#81394c8bf3806f9d4c29910baab84314 https://git-man-page-generator.lokaltog.net/#81394c8bf3806f9...

sonnyblarney 8y ago

This is funny, but in reality it's not. Git is one of the most amazing, powerful tools ever conceived, with one of the must byzantine and ridiculously designed 'interfaces' ever conceived. People confuse the raw power of a tech, with how well it can be feasibly used. Sadly, due to the later issues, git will only ever be a shadow of what it could have been. With all due respect to Linus, who'd be the first to admit he's not very good at UI stuff (I mean command line as well)... it's truly a sad thing. This is a major 'problem that needs to be solved' I'm interested to see how it could evolve into something 'better'.

karmakaze 8y ago
I don't think the complexity of git's command options is a UI problem. It results from the basis of its operation. We could change some names, add or remove some concepts to how some of the operations are performed, but there are simply a large number of actions to handle many edge cases. A better solution for prose was to always be merging with live multiple collaborator updates. Conflicts are visible in real-time. I can't see something like this would work with code. Hmm interesting... unless we only allow additions and refactorings to working checkpoints.
- P_I_Staker 8y ago
  Yes, I don't really understand all the people trying to "fix git". Git's fine, though the complexity makes it challenging, especially for new users. However the complexity is a direct result of useful features. "Keeping it simple" is great, except when the complexity is needed. I'm hard pressed to name any features I could do without.
  - sonnyblarney 8y ago
    There are two problems: one of inherent complexity, one of UI. First - the UI is a mess, and that should have been fixed. It would make a big difference. Second - is the inherent complexity. That's a good point, but I feel many things could be hidden or obfuscated. Most poignantly, Git does something that most of us do not need: it was designed to work as a 'completely distributed system', i.e. for open source. Almost none of us do that. 95% of uses cases related to you and I working collaboratively, on a project together. The need to have repos which are essentially totally distinct from one another is a huge source of complexity and it simply doesn't need to exist in most cases. So Git is basically an 'admin level tool' that is commonly used in scenarios for which it wasn't meant to be used, with a confusing interface. It's costing a lot of time and money and headaches, I do believe someone may come along eventually and fix it. This thread is essentially evidence of this - see how many people have difficult teaching what should essentially be a simple thing in most cases. Way too many very smart people still spend too much time clustering around in git.