I should be the one to be angry git
-
fatal: Paths with -a does not make sense you stupid moron.
That seems a little passive aggressive, right?
"you stupid moron" added by me but it felt like git was telling me that
-
-
"you stupid moron" added by me but it felt like git was telling me that
You get no sympathy until it tries to
SPANK
you.
-
It's actually catching potential errors (caused by Linux's moronic refusal to enforce any kind of limits on file names) before they happen.
So... I approve of this. Don't put -a in a path.
-
```
fatal: Paths with -a does not make senseLeaving aside the obvious gramming, that error is about as useful as a grain of sand in your eye. Great, it doesn't make sense. Why doesn't it?
-
Oh I assumed he edited more than just adding moron.
Yes that grammar is atrocious, and the error (like all Git errors) is far too vague and doesn't include any possible resolution. Because Git is a piece of shit.
But it's not that bad. Not by Git standards.
-
I assume because directories aren't versioned?
-
What did you actually run or tried to do, you naughty programmer?
-
Jeez... It was just a typo but I found funny how harsh git was with me.
-
Tell the command to automatically stage files that have been modified and deleted, but new files you have not told Git about are not affected.
I've never used that flag as I always review my changes with
git add -p
before committing them.
-
I use status and diff but for some small changes it's a one step
commit -a -m ""
-
-
Great, it doesn't make sense. Why doesn't it?
I've not checked, but my first instinct would be to assume that -a means "all".
-
I assume because directories aren't versioned?
What does that even mean (independently of versioning the contents, which git does do)?