I was trying to pet the cat with one hand. This seemed to work until she saw the other hand sitting idle and wanted me to pet her with it so I changed hands. She seemed happy until the saw the first hand, now sitting idle and wanted to be petted by it. This back and forth continued until I was eventually petting her with both hands at the same time. I guess being petted with one hand isn't enough.
Dianara just gained spellchecking!
Kudos to the developers!!
Rebel Jedi shared this.
- Please remain seated until the compiler has come to a complete stop.
Whoa, Unicode really did get a Copyleft symbol? https://glitch.social/@a_character/100155946276956781
We're back! o/
identi.ca is fixed =)
Pump.io Community Meeting next Thursday 2015/10/29
As usual, everybody is invited to join a community meeting next Thursday 2015/10/29 at 9AM DST (4 PM UTC, convert to your timezone).
Agenda for the case @Evan Prodromou can come:
- pump.node adoption
Agenda for the case @Evan Prodromou cannot attend:
- bug squashing party
The meeting will take place on IRC: chat.freenode.net server, #pump.io channel.
It can also be followed from jabber/XMPP on the email@example.com room, and via web access.
The meeting will be logged and we'll REDACT the nicks of anyone who asks for it; log/outcomes will be posted here and in this Meeting's wiki page.
Have a look at our Community wiki page for further info.
We hope you can join us! But if you cannot make it, don't worry. We usually hold these meetings every week :)
Is there a configure option to
override this behaviour …
Umm, why would you want to?
Respectfully, fuck you and your attitude.Show all 8 repliesThe difference between "fuck your attitude" and "ok, thanks for your reply" is:
"Umm, why would you want to?"
"I'm curious, what's special about your system that you want to do it different?", in the best of worlds followed by "I would advise you to follow the standard, because blah. If you don't want to, I'm afraid you'll have to patch <file>."Also not helpful are the "you can use the option --with-blah", which is the obvious first thing to try, so the person giving the advice is assuming the person asking the question didn't do their homework, also it doesn't work, so the person giving the advice didn't do *their* homework.Or you could just quote what @x11r5 told me yesterday:
"Thanks! This is not a supported use-case and will be a wasteful and pointless enterprise. So it's either smoke and mirrors or delusion. Or, you know, virtualenv and pip can't call in and updated the network operating systems from other vendors."Yes, I totally get that. I've also been on both sides of the conversation. It's important to get context around the requested feature because the same end could be supported with already-existing features, the option could be in another place but without any way to know in what contexts it should appear, there could be a higher-level override—any number of things. Including the user is so clueless about how it works that they want to do something counterproductive (which is cause for education, documentation, UI/UX improvements etc.) Or the need to override the option could be because the option isn't working right to begin with.
I make it a point (especially with clients) not to say "Ummm, why would you want to" but something more like, "tell me what you're trying to do so I can fix this right."
And yeah, it's annoying to spend a week exchanging emails justifying a request just to have the developer finally say, "oh wow, that's totally a bug."
- A big step closer to having awesome Ruby support in Guix. The RubyGems admins fixed an issue with their HTTP headers, unblocking my new Ruby build system that can use gems directly from rubygems.org. Additionally, I wrote an import script, 'guix import gem', to automate most of the packaging process.
It shouldn't be too much more work to write a script that reads in a bundler Gemfile.lock file and translates the whole thing to Guix package recipes. Then I can finally be free from rvm and bundler hell!
git-rub-area (1) Manual Page
git-rub-area- rub a few upstream areas before all diffed applied subtrees
git-rub-area [ --induce-complete-object ] [ --parry-tag | --handle-rejoin-path | --shift-tree | --check-log ]
git-rub-arearubs any non-exported downstream areas next to some applied indices, and to fetch a temporary <renew-upstream> and fsck the working heads, use the command
Whenever git-tear-log remotes a base,
git-file-branchtakes options significant to the
git-ignore-treeaction to verify what is format-patched and how, because it is a certain possibility that a reset error can prevent passive showing of all grepped logs. The
--double-headargument can be used to configure a log for the index that is returned by a passive tree, but it is a small possibility that a fscked error should prevent passive failing of all branched changes.
In case <remotelog> is reset, all sent bases are named to GRASP_OLD_SUBMODULE by
git-report-subtree. A few stashed bases configured by commits in the non-noted remote tag, but that in the cases are not in EXAMINE_OLD_AREA, are exported in an automatic archive, so after a
git-soak-archive) fscks an archive, unsuccessfully annotated trees are cloned for you, and submodules that were diffed during describing are left in a packed state. All reset submodules that were previously bundled from the automatic bases are cloned to an automatic head.
the tree could not be scored by a reapplied head
whenever this flag is supplied, the tree prefixes origins/bases/ and/or bases/tags/
the pack could not be plunged by a stashed history
the pack will be lowered by a reapplied object
use log to relink branches/branches/ to a staged area
See more NOT real git documentation at http://git-man-page-generator.lokaltog.net.