Viewing profile — u801e

I've been doing this with vim for several years since they added the terminal feature in vim version 8.

Would they notice that she had not badged in or logged in on Monday morning? Unless she had already taken time off starting Monday.

> Interestingly though I still use NNTP (News) daily. One community I participate in still makes use of a (private) NNTP server as the forum of choice. Only the lightest amount of …

> I don't think they were suggesting to review the individual commits, rather the (individual) commit messages. That's a good point. > Commit messages are text, so you could have a…

> It's an awful shame that GitHub doesn't allow commenting on commit messages. You actually can comment on a commit itself. I'm in the habit on middle-clicking on the sha1 link of …

> A commit is required to have a bug id. The bug tracker has entire discussions of what lead to the commit Companies do change bug trackers and ticketing systems and those links ma…

I can go up and down unobstructed stairs without any issues, but I have back problems which keep me from doing heavy lifting and I'm in no condition to jump or climb over a sofa in…

> A couch and a fire and that couch can't be pushed over or jumped over. Not everyone is young and in shape to push couches or jump over them.

> I like how vim is modal, but some Windows shortcuts (like Control-C) just make too much sense to given them up on Linux Ctrl-C does work in the GUI. That said, one thing I like a…

> IRC simply a different use case than a forum. Except that newer products like Slack and email providers with their conversation view are conflating the two use cases. Slack tries…

Or a usenet newsgroup.

Yet, when I'm browsing Facebook, I frequently encouter an issue where the brower tab process starts allocating 5% or more of resident memory (on a 16 GB memory machine). On the oth…

I remember the days when having 16 MB of memory was plenty to do that.

It's too bad yenc didn't take the place of base64 for email.

At least on my system, it's not an issue: $ date --date="@2200000000" Sun Sep 18 07:06:40 PM EDT 2039

As for what the future holds: $ date --date="@1800000000" Fri Jan 15 03:00:00 AM EST 2027 $ date --date="@1900000000" Sun Mar 17 01:46:40 PM EDT 2030 $ date --date="@2000000000" Tu…

> > * enables use of git bisect to locate bugs > This is really only viable if each intermediate commit on a development branch is intended to be bug free. git rebase has an --exec…

Another good reason is that having a small commit that changes just one thing is a lot easier to revert without encountering conflicts, even after other features have been committe…

> Even emails were not a proper replacement. Initially free providers only supported sending/receiving emails with 1 to 5 MB attachments. Pretty much every ISP provided an email ad…

> Indeed, but trying to revert lots of tiny commits in one unit is no better. You shouldn't have to revert a lot of tiny commits if the bug is due to just one of those commits. > T…

Not only that, they also result in commits that change a lot of files and make many changes in each file. Try to revert one of those commits is difficult after other changes have b…

> The point is [the squash commit method] enables bisect workflows that don’t suck. If half the commits in a tree are “fix misc derp” or “test passes now”, that workflow isn’t poss…

Copy-paste may not work depending on how the email client renders the email. For example, if the email client doesn't preserve prefixed whitespace, then the resulting patch may be …

> I don't yet see how that is different from just... a sequence of commits The difference is a sequence of commits that implement a feature where each commit basically is a logical…

Save the email to your local machine (in gmail, click the 3 dots and choose download message). Then run git am