-
Notifications
You must be signed in to change notification settings - Fork 278
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
Any comment about upcoming Git Rev News edition 66 #453
Comments
I got really occupied this month. So, I wasn't able to get around to finding a person to interview. Sorry for the delayed note. I'll be sure to find someone for the next month's edition. I'm open to suggestions for interviewing if anyone has someone in mind 🙂. |
@sivaraam no worries! I have been very busy too. And that's in fact why I postponed publication to Thursday 27th instead of Wednesday 26th. |
In 0c8a356, I made a small correction to the relative time of a referenced e-mail. |
My links have landed in 28d7512 I see that there is git-mv: improve error message for conflicted file reviewed.
|
Added some typo fixes and rephrasings, and edited the SourceGraph Cloud
site description in 35dd8c2.
@chriscool Have a nice vacation time!
|
Added the How can I search git log with ceratin keyword but without the other keyword? story in e39b0ed -- mainly there for the last quote... |
@jnareb great, thanks! |
Thanks @sivaraam! |
In 5421a7c, I added a fixed a few minor things I happened to notice during my read.
Yeah, have a great time :) |
Thanks @mjaix and sorry for the mistake! |
Thanks @mjaix, @jnareb and @sivaraam for your work on this edition! It's published and announced on the mailing list: https://lore.kernel.org/git/CAP8UFD3uXLS3TqeQ=nKJqfkjMTMBfBWMSmb24=mAjSt14hsdCg@mail.gmail.com/ |
A currently mostly empty draft is there:
https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-66.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 26th 2020!
Thanks!
cc @jnareb @mjaix @sivaraam @gitster
The text was updated successfully, but these errors were encountered: