Any comment about upcoming Git Rev News edition 98
chriscool opened this issue · 13 comments
A currently mostly empty draft is there:
https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-98.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 26th 2023!
Thanks!
A few discussion that might be worth considering adding to this Git Rev News according to @jnareb:
- Question: How range-diff lapjv algorithm work
- git bug: Perl compatible regular expressions do not work as expected,
but I think it is not finished yet
In this edition we could possibly list GSoC contributor proposal rankings (due 27 April 2023 at 18:00 UTC), though accepted proposals (if any) need to be left to next edition.
Another support story which I have stumbled upon:
- Weird behavior of 'git log --before' or 'git log --date-order': Commits from 2011 are treated to be before 1980 - caused by two separate parsers of commit headers, and their parsing of malformed authorship field.
I wonder if there is a place in Git Rev News to mention new commands, like git replay, but I expect it would be covered by some Git Highlights that happen from time to time on GitHub Blog, or by similar piece somewhere else. Then it would be enough to simply include said link.
By the way, if we want to have a survey for edition 100, we need to have it prepared for internal survey about survey for the next edition: 99th. ;-)
My links have been added in a81f0c1 .
By the way, would (rare) links of Git-related or version-control related scientific publications, like in this edition, be something worth having in Git Rev News?
In this edition we could possibly list GSoC contributor proposal rankings (due 27 April 2023 at 18:00 UTC), though accepted proposals (if any) need to be left to next edition.
@jnareb unfortunately Google doesn't want us to disclose clues about who we are likely or not to accept before everything has been decided and they have sent an email to the applicants, which should happen on May 5th. So I think we should not disclose anything before that time. So let's just talk about those who have been accepted in the next edition.
By the way, if we want to have a survey for edition 100, we need to have it prepared for internal survey about survey for the next edition: 99th. ;-)
@jnareb Yeah, it would be nice if we could have a survey ready for edition 100. I think we should focus on finalizing the question list soon. I have asked you and @mjaix a few questions in the issue. Hopefully this will help speed things up.
Another support story which I have stumbled upon:
Weird behavior of 'git log --before' or 'git log --date-order': Commits from 2011 are treated to be before 1980 - caused by two separate parsers of commit headers, and their parsing of malformed authorship field.
Yeah, very interesting but there are messages from yesterday in this thread, so I would prefer to wait a bit and perhaps use it for the next edition.
I wonder if there is a place in Git Rev News to mention new commands, like git replay, but I expect it would be covered by some Git Highlights that happen from time to time on GitHub Blog, or by similar piece somewhere else. Then it would be enough to simply include said link.
Yeah, I think such highlights or sometimes blog posts or presentations by some of the contributors are enough.
The discussion seems very short and I am not sure there is much to learn in it, except for the fact that git range-diff uses a complex algorithm.
git bug: Perl compatible regular expressions do not work as expected, but I think it is not finished yet
Unfortunately it seems that the discussion didn't come to an interesting conclusion or even a patch.
So I think I will look for something else.
Published and announced in: https://lore.kernel.org/git/CAP8UFD13nBVpRs_N=fjYk=aCoDtFRoAmwZz9_H98e4mb-wWiYA@mail.gmail.com/