Friday. 17:56. Time to go home.

> git add *
> git commit -m 'wip, feature almost done, need to test'
> git pu... [BIG FAT BSOD]

fuck it, I'm out

  • 4
    Shitty hardware and driver issues? Definitely not Windows' fault, it never is! 🙃
  • 2
    @Condor lxsys [or smth of sorts] in message suggesting wsl died. No idea how drivers or hw could be related 😁
  • 7
    @netikras but but.. it can't be Windows' fault! I never have issues with it, therefore it doesn't have issues at all! It can't possibly be that Windows is a steaming pile of shit that crashes seemingly at random, it can't possibly be!!! 😖

    There's a reason why I put most critical stuff in screen sessions when I'm working on remote servers from Windows 🙃
  • 2
    @Condor you know, you must be right. Since windows is the superior os it's not its fault it crashed. It must be the linux subsystem that did smth bad and meddled with windows and made it crash. BAD linux! BAD!
  • 1
    Is there a difference between 'git add *' and 'git add .'?
  • 1

    add * means add all files in the current directory, except for files, whose name begin with a dot. This is your shell functionality and Git only ever receives a list of files.

    add . has no special meaning in your shell, and thus Git adds the entire directory recursively, which is almost the same, but including files whose names begin with a dot.
  • 0
    @Commodore Oh ok, thanks
  • 1
    At least it’s commited.. imagine pc crash while still adding.. 😖
  • 0
    @netikras how is that any better?
  • 0
    @Commodore eh? How's what better?
  • 2
    @netikras ow my bad. I was replying to @pai-shinoda. No idea how I messed that up.
  • 1
    @Commodore cause you still have the commit locally.
  • 0
    All good until you want to work on something at home and you realise you haven't pushed the commit 🙃
Your Job Suck?
Get a Better Job
Add Comment