WingNews logo WingNews GitHub [2]
top | item 12417419

Git 2.10 has been released

205 points| dwaxe | 9 years ago |github.com | reply

36 comments

order
[+] Radim|9 years ago|reply
Meta: Beautifully written release summary, including hyperlinks and animated gif "demos".

Inspirational for our own releases :-)

[+] paradite|9 years ago|reply
Nice formatting aside, I am slightly concerned that GitHub "releasing a release note" for Git would further blur the distinction between the two for new programmers.

If I were new to Git and GitHub, I would have thought that Git is a product of the company GitHub.

Edit: After searching through git repo and official site, I could not find any nicely "rendered" release note beyond the official release note in raw markdown here: https://raw.githubusercontent.com/git/git/master/Documentati... , so I think GitHub is doing us a good thing here by giving a high level summary and actually rendering the markdown properly.

[+] SquareWheel|9 years ago|reply
I find the gifs make the text around them far harder to focus on. I'd much prefer they only played on click or hover.
[+] raus22|9 years ago|reply
and with humour: > Git's internal date-formatting code can now correctly show dates past the year 2100. Phew, fixed with only 84 years to spare.
[+] DigitalJack|9 years ago|reply
Do you know what they might have used to make the gifs?
[+] abhinavk|9 years ago|reply
Interestingly, git-scm.com is still serving Git 2.9.3 right now.
[+] SOLAR_FIELDS|9 years ago|reply
This is great and all, but do status bars and terminal colorings really warrant this kind of fanfare? I love git and I'm very happy that they are constantly releasing new stuff, but I think we should draw a line somewhere on what really matters and what doesn't as far as news coverage.
[+] has2k1|9 years ago|reply
The news is on github, it specialises in everything git and on the git subject they can choose to shine the light wherever and it will not be out-of-place.

Maybe you could limit the criticism to the fact that it has been submitted to HN and voted onto the front page, which would be a criticism of distribution medium and of the medium consuming masses.

[+] hoodoof|9 years ago|reply
It seems so easy to include a command line option to specify which PEM file to use but git just won't do it.

Yes I know there are ways around it and config files you can set up, but heck, it's just a command line "use this PEM file". It's not hard.

[+] jxy|9 years ago|reply
Does anybody really care about the progress meters? Those useless numbers! You can try to tell me you are not stuck every half second or so, but I don't want to see all the noise. I'd rather it not print out anything by default unless I ask for it or it fails.

Why do git developers concern about the colored output? It's completely unrelated to SCM at all. I love the functionality. But it shouldn't be only for git. Can we have a separate utility that reads a diff and gloriously print out the contents, all by itself, and only that?

I really don't want to see git becomes another bloatware.

[+] onion2k|9 years ago|reply
Use the --quiet flag to turn off most output and don't bother defining any colors if you don't like them. Now git is how you like it. For diffs, try git difftool.
[+] addicted|9 years ago|reply
1) The progress meters is important. The scenarios in which this progress meter would matter, would lead to users thinking something strange went wrong and their push did not succeed because of the lack of the progress meters. Besides that, it's a UI manifestation of a bug that would have led to pushes in certain scenarios not working.

2) As long as GIT diff exists, making it more usable should certainly be a core part of changes to GIT diff. There are many utilities you can use for GIT diffs easily enough instead of the base diff. But I like the fact that if I'm at a machine where my preferred utilities are not setup, I still have a very usable diff built into GIT.