Skip to content

Any comment about upcoming Git Rev News edition 102 #656

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
chriscool opened this issue Jul 31, 2023 · 17 comments
Closed

Any comment about upcoming Git Rev News edition 102 #656

chriscool opened this issue Jul 31, 2023 · 17 comments

Comments

@chriscool
Copy link
Collaborator

A currently mostly empty draft is there:

https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-102.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 August 30th 2023!

Thanks!

cc @jnareb @mjaix @sivaraam @gitster

@chriscool
Copy link
Collaborator Author

Note to self: @jnareb left the following comment on the issue for the previous edition:

I wonder if it be worth including the series of instructions on how to obfuscate timestamps in Git called Git-Privacy - see also discussion on git mailing list.

@jnareb
Copy link
Member

jnareb commented Aug 12, 2023

It may become something interesting:

@chriscool
Copy link
Collaborator Author

Sorry but I caught a cold just after coming back from vacation and now I am quite sick and won't be able to send a draft today. Will try to do it tomorrow though.

@jnareb
Copy link
Member

jnareb commented Aug 30, 2023

Would Google Summer of Code be resolved?

@sivaraam
Copy link
Member

The final evaluation deadline for this year is September 4 and the results would be announced only by September 5 [ timeline ].

So, I think we could talk about the GSoC conclusion only in the next edition.

@chriscool
Copy link
Collaborator Author

Yeah, right. We have filled out Kousik's evaluation already but we cannot talk about this yet.

@chriscool
Copy link
Collaborator Author

Just sent the draft email. It's not yet on https://lore.kernel.org/git/ or https://public-inbox.org/git/ though.

@jnareb
Copy link
Member

jnareb commented Aug 30, 2023

My links have landed in 33561ae (and got merged in).

@chriscool
Copy link
Collaborator Author

@chriscool
Copy link
Collaborator Author

@jnareb thanks for your links!

By the way I think the following link might be interesting too:

https://about.gitlab.com/blog/2023/08/28/sha256-support-in-gitaly/

@jnareb
Copy link
Member

jnareb commented Aug 31, 2023

By the way I think the following link might be interesting too:

https://about.gitlab.com/blog/2023/08/28/sha256-support-in-gitaly/

Added in 5bd4366. Thanks for the link.

@chriscool
Copy link
Collaborator Author

chriscool commented Aug 31, 2023

@mjaix, I just merged a typo and grammo fix PR from @stepnem (thanks!) in 4caa3a6.

@mjaix
Copy link
Contributor

mjaix commented Aug 31, 2023 via email

@mjaix
Copy link
Contributor

mjaix commented Aug 31, 2023 via email

@chriscool
Copy link
Collaborator Author

@Christcool It went somewhat late on my side, too ... about to start the proof- reading now. Hope that's ok.

@mjaix yeah, sure it's Ok thanks for your fixes!

@chriscool
Copy link
Collaborator Author

It may become something interesting:

* [Fetching too many tags?](https://public-inbox.org/git/[email protected]/t/#u) - contains interesting info about how Git fetches from remote repository

@jnareb thanks for this suggestion! I wrote an article based on your previous suggestion (about the "Git Privacy" email thread) for this edition, but I may take a look at this for next one.

@chriscool
Copy link
Collaborator Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants