| 06:40 |
feedbot |
http://ossasepia.com/2020/06/19/after-the-rain/ << Ossa Sepia -- After the Rain |
| |
~ 2 hours 45 minutes ~ |
| 09:25 |
diana_coman |
ossabot is fully retired, don't expect it back (nor its site, nor the ftp, nor anything from the whole pile of resources of all sorts that are finally freed up for more productive use); archives are and will remain at http://ossasepia.com/raw-logs-and-archives/ ; real-time and past logs are and will remain permanent at http://ossasepia.com/category/logs/ |
| |
~ 1 hours 36 minutes ~ |
| 11:02 |
feedbot |
http://trilema.com/2020/the-story-of-kitty-and-her-kitten/ << Trilema -- The story of Kitty and her kitten |
| |
~ 3 hours 26 minutes ~ |
| 14:28 |
diana_coman |
http://ossasepia.com/2020/05/03/ossasepia-logs-for-may-2020/#1026261 - bvt, in potentially interesting follow ups on this, on one hand it turned out that at least in some cases the "reverted file" was not even desirable ie an artefact of other trimmings-on-the-large-codebase but on the other hand I *did* end up having to pretty much script the "point out the exact offending file, stupid" part, |
| 14:28 |
diana_coman |
even if a quick and dirty/partial piped cmd line sort of thing. |
| 14:28 |
sonofawitch |
2020-05-23 20:40:06 (#ossasepia) diana_coman: and yeah, comment gets one out of it - but the main issue was figuring out *where* the exact revert was |
| 14:30 |
diana_coman |
the conclusion from use is therefore that this sort of "loop" may or may not be fine, up to operator to decide on a case by case basis; but there has to be a better way to point to the actual problem, even if it ends up perhaps as a separate command or even outside v.sh entirely. |