one-liner

However, if you really feel it's off-topic, you should probably flag it instead of posting a one-liner complaint.

Isn't the whole point of Git that you can just go and setup an upstream somewhere else with a one-liner?

Here it happens to be because it's a one-liner expression.

So many one-liner garbage comments, no way to downvote.

(Well not as simple, but still a human-readable one-liner that works on nearly all Linux systems.) You don't, really.

Also, if your code is a simple one-liner, it does not really add too much benefit to name everything, if it is obvious from the (very local) context.

I won't downvote you either, but to answer your first question, it is group think because it is a vague one-liner that puts down a rather great accomplishment from an underdog in favor of a mainstream brand name.

(Well not as simple, but still a human-readable one-liner that works on nearly all Linux systems.) I thought maybe a single-line invocation might piggy-back on SSL as follows: - get a server's public key that is not online or able to answer requests (because if it were it couldn't be airgapped) - but still use the key to verify the script that's downloaded from the server that is online.

I think three months later I might have gotten a one-liner saying they had gone in "a different direction" or some bullshit like that.

Your example rejection strikes me as overly verbose with little substance, is almost comically apologetic, and again boils down to the exact same one-liner of "You're not a good fit at this time." It's really a long-winded way to convey the exact same (lack of) message, but with tidbits of one's resume and lots of apology sprinkled in to seemingly convey depth and empathy.

Where by "roughly the same" you mean "twice as high", and by "black" you mean "black and hispanic", and, of course, the demography that creates those statistics and confounds simple comparisons like that is left entirely out of your one-liner.

If you're a virtualenv user, I use this one-liner to start load a virtualenv named after the current directory: alias v='workon "${PWD##*/}"' Also, I really like the -p flag of mkdir (creating child directories as needed, without failing if one doesn't exist) alias mkdir='mkdir -p' # i.e.