Git 2.47 Released With Improvements & Encouraging More Positive Code Reviews

[Britoid]

No one will read that notice other than the Phoronix readers currently viewing this post.

[Danny3]

when will they solve the empty folders not being tracked problem?

[discordian]

No one will read that notice other than the Phoronix readers currently viewing this post.

Yeah, wonder why this was singled out... engagement farming much?

[klh_io]

when will they solve the empty folders not being tracked problem?

Probably when it becomes a problem? Think about directories as file prefixes and you can see how tracking empty ones is pointless.

[colejohnson66]

when will they solve the empty folders not being tracked problem?

If it's an issue for your specific repository, the convention is to do one of two things:

1. Add a .gitignore that says to exclude everything except the .gitignore itself:
   *
   !.gitignore
2. Add a .gitkeep file (name is just convention), optionally with an explanation for the file contents

In addition to what klh_io said, if you think of git as a file tracker, then it makes sense that empty directories aren't tracked. Git does have the concept of "tree objects" that are similar to directories, but I'd bet pointing a tree at an empty object would break some things.

[TheMightyBuzzard]

Why would a few sentences encouraging people to be kinder to other human beings produce that first impression in you? Seems a bit pathological.




Ah, I see you know nothing about effective people management.

Says the guy who's never even managed younger siblings to the guy who's been paying employees for decades.

[gotar]

Why would a few sentences encouraging people to be kinder to other human beings produce that first impression in you? Seems a bit pathological.

Because documentation should be short and simple? With no ambiguous or subjective terms.
Git was failing hard with this - with all the "undocumentations" (self-referencing or using unknown terms) and single commands doing radically different things with some switches,

[Citan]

Another release for the nerds.
I would like to see Git focusing on becoming more user-friendly and more approachable to non-tech guys and people who aren't so smart or are new to development too.

I have to agree with others here. Git CLI is far sufficiently understandable and "intuitive" as-is. I had some gripe for a long time about the difference of behaviour about some commands like checkout depending on their arguments, but that was already resolved years ago by adding explicit commands for each use-case.

This text sounds a bit ridiculous tbh.
At first I thought this is meant as a joke. Is it the first of April?
Why doesn't it mention giving a negative review when the code sucks? Very one-sided.
Seriously??!

Because apparently Git devs finally understood on their own how being *always constructive and open-minded* is the optimal way to best efficiency?
This is not at all incompatible with providing fair (and possibly harsh) criticism on the submitted code mind you.
It's just about showing your own self-awareness of your bias and limitation and showing your non-personal, non-judgemental analysis which goal is not "undermine commiter's effort or reputation" but "contribute to the betterment of the sofware, whomever has worked into it".

when will they solve the empty folders not being tracked problem?

Probably never? Because as far as I remember it was a conscious design choice to avoid having to specify extra lines in gitignore whenever you had a new "temporary folder" (empty in dev, just filled at runtime or compilation) or "created in case of future use-case" folder created.
And probably because it was the path of lest effort for Git designers (less work to adapt gitignore if empty folders ignored rather than if taken into account by default).
It's as often a matter of half-empty vs half-full glass if you will.

The best you could probably get, although that would be indeed an interesting feature if it can get traction enough, would be an option to "reverse" the "global behaviour" in the "git project configuration file"... You're welcome to create a feature request on git for that if it feels pertinent for you, I'll happily +1 it.

[bug77]

Somehow, considering how much good git did to VCSes in general (yes, I know it has a very steep learning curve), calling it "immensely popular" seems like an understatement to me.

[TheMightyBuzzard]

Because apparently Git devs finally understood on their own how being *always constructive and open-minded* is the optimal way to best efficiency?

Constructive and open-minded are not the same as unjustly praising. They in fact specifically exclude praise for mediocrity unless mediocrity is your aim in the first place.