Any comment about upcoming Git Rev News edition 86
chriscool opened this issue · comments
A currently mostly empty draft is there:
https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-86.md
Feel free to comment in this issue, suggest topics, suggest persons to interview, or use the edit button (that looks like a pen) to edit and create a pull request with the changes you would like.
Let's try to publish this edition on Wednesday April 27th 2022!
Thanks!
Maybe we could talk a bit about the git-scm.com Heroku credits update thread. I am also interested in the recent threads that involved Linus.
Should we avoid political-related news in Git Rev News, namely:
- GitHub suspends accounts of Russian devs at sanctioned companies
- GitHub suspending Russian accounts deleted project history and pull requests - with an update
Let's try to publish this edition on Wednesday April 27th 2022!
I guess this needs to be updated.
My links have landed in b0f943a
@jnareb thanks for your links!
And yeah, I am very very late, (yeah more than usual) sorry. I will send the draft to the mailing list really soon now and hopefully we can publish late on May 1. I'd like the date to still be April 30th though, so that it's it doesn't look like there are 2 editions in May 2022 and 0 in April 2022.
I still plan to talk a bit about the git-scm.com Heroku credits update thread, after the draft is sent though.
I don't think we should avoid political-related news in Git Rev News, especially when we just link to such news.
Added my tiny fixes, and changed the Vershd marketing example to a citation from a letter by its CEO to my @work email address (Jakub: feel free to revert, but IMHO it's real FUD), [...]
Yes, it is. I agree that it is FUD, though it is more present with those cold-open letters by Vershd CEO (I also got one), than on the webpage itself.
Here is my response (well, part of it):
The reason I [CEO of Vershd] asked is because we chatted with many software developers who related that Git is very powerful, but can easily destroy days of work in just seconds and requires thousands of keyboard commands and parameters.
I would say that it is an exaggeration, on the brink of spreading FUD (Fear, Uncertainty, and Doubt marketing / propaganda tactics).
(By the way, Gmail spam filter also thinks so, and due to combination of this e-mail subject and the body of this e-mail, it put it in the Spam folder.)
Yes, that is true that Git consists of hundreds of commands and subcommands combinations (I do not count so-called "plumbing" commands, which are for scripting, not for the end user), each with tens of parameters, and that using Git GUI can help there. However, in normal use (that what's various GUIs for Git cover), you use only a small subset of them, certainly not "thousands of command line commands and parameters".
Git also tries quite hard to preserve your precious work. There are destructive operations, of course, but they all require
--forceor--hardoptions to be present. With reflog (which admittedly you need to know about and know how to use) you should be able to undo most mistakes, certainly those that would loose otherwise "days of work" - I assume here that one would not work that long on a single commit.Of course, Git is not without faults, and as a project which developed in a long evolutionary process, it is not without warts in its user interface. There are and were many projects that try to fix problems with Git, those accidental complexities, such as Easy Git (eg), Gitless, and various Git GUIs.
@mjaix thanks for your fixes!
@jnareb and @mjaix thanks for handling the Vershd propaganda!
Edition published and announced:
https://lore.kernel.org/git/CAP8UFD08-6XpDSXYMShLFOiHfwbaqbus9axgmGG1+SAP9RgXOw@mail.gmail.com/
I forgot talking about the git-scm.com Heroku credits update thread, but I plan to do it in the next edition.