search

git / git.github.io

Git Developer Pages (This is NOT the place to discuss Git issues. See: https://git-scm.com/community)
https://git.github.io
306 stars 278 forks source link

Any comment about upcoming Git Rev News edition 23 #209

Closed chriscool closed 7 years ago

chriscool commented 7 years ago

A currently mostly empty draft is there:

https://github.com/git/git.github.io/blob/master/rev_news/drafts/edition-23.md

Feel free to comment in this issue, or to use the edit button (that looks like a pen) to edit and create a pull request with the changes you would like.

Thanks!

cc @tfnico @jnareb @mjaix @gitster

chriscool commented 7 years ago

I am not sure it will be possible to publish this edition on Wednesday January 18th as I am in Cancun with GitLab these days, and there are things planned all the time.

Also my plane to go back to Paris leaves Cancun at 10pm on the 17th, and after a stop in Frankfurt I will arrive in Paris at around 5pm on the18th.

So I will see maybe it's not too bad if we publish on Friday January 20th instead?

jnareb commented 7 years ago

Friday January 20th is fine to me.

-- Jakub Narębski

mhagger commented 7 years ago

Maybe you want to mention git-test, which I announced here and which has already grown a bunch of new features since the initial announcement.

mjaix commented 7 years ago

Hi Christian, hope you had a good trip. I will try to proofread whatever is there tomorrow evening ... On Sat, 2017-01-14 at 03:39 -0800, Jakub Narębski wrote:

Friday January 20th is fine to me.

-- Dipl.-Ing. Markus Jansen Alte Vaalser Str. 40a Mob. +49 172 2742003 52074 Aachen/Aix-la-chapelle/Aken/Oche Tel. +49 241 5592439 Deutschland/Allemagne/Germany/Duitsland/Tyskland Fax +49 241 5592441 mja@jansen-preisler.de

chriscool commented 7 years ago

I wanted to finish the draft before coming back from Mexico, but I couldn't, so let's plan to publish this edition on Wednesday January 25th.

tfnico commented 7 years ago

Roger that. I'll wait with my links until then.

By the way, I'll be at Git Merge in Brussels with my recording gear again. Finally time to make some new GitMinutes episodes. Hope to see you all there!

On Thu, Jan 19, 2017 at 6:07 PM, Christian Couder notifications@github.com wrote:

I wanted to finish the draft before coming back from Mexico, but I couldn't, so let's plan to publish this edition on Wednesday January 25th.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/git/git.github.io/issues/209#issuecomment-273835976, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPYn0cTu3CrDi0fFoT75NNKIu1vtAzRks5rT5hcgaJpZM4LM7KQ .

jacob-keller commented 7 years ago

There was an interesting discussion about adding shorthand notation for refs recently viewed through the log, and Peff ended up showing his suggestion for urxvt terminals that lets him copy sha1 ids found on screen. Might be worth sharing this.

chriscool commented 7 years ago

@jacob-keller I think you mean this discussion: https://public-inbox.org/git/20170120102249.15572-1-pclouds@gmail.com/ Thanks for the suggestion! I will try to write about it in the next edition (edition 24).

chriscool commented 7 years ago

@tfnico I'll also be at the Git Merge in Brussels. Yeah I am also looking forward to meeting everyone!

jnareb commented 7 years ago

What is the cutoff date for edition 23?

chriscool commented 7 years ago

@jnareb I'd like to publish edition 23 on Wednesday January 25th at around 12:00 CET. If you want to write an article it would be better to add it before Tuesday January 24th. For other smaller things, I think it's ok to make changes until the last minute.

jnareb commented 7 years ago

Sorry, what I wanted to ask is what is the cutoff date for the material to be in edition 23, that is what is latest post from git mailing list that should be considered for edition 23, and which one should be left for edition 24?

chriscool commented 7 years ago

Ok, about the material, I think it's better to talk about discussions or mailing list threads that have been over for at least a week. And if possible the main thread or discussion should have started during the previous month or maybe the first days of the current month.

chriscool commented 7 years ago

@mhagger I just mentioned git-test in the __Git tools and sites__ section. Maybe we can improve on that by adding a few more line of description or by writing a small article about it (maybe for the next edition).

mhagger commented 7 years ago

I just mentioned git-test in the __Git tools and sites__ section. Maybe we can improve on that by adding a few more line of description or by writing a small article about it (maybe for the next edition).

@chriscool: Thanks. If there's still time for changes, I'd suggest adding a link to the git-test repository itself, which is more up-to-date than the mailing list announcement. If you want to add a slightly longer blurb, it could be

git-test - A script for running automated tests across multiple commits and keeping track of the results. First you define your test using a command like git test add 'make -j8 test'. Then you run the test against a range of commits using git test run master..mybranch. You can run the second command as often as you like; git test will only test commits that it hasn't already tested.

tfnico commented 7 years ago

@chriscool my links have landed.

jnareb commented 7 years ago

@chriscool my links have also landed

I have started adding threads bookmarked/starred in my newsreader.

A question: where to put description of thread that started as support, and ended with a patch (namely Test failures when Git is built with libpcre and grep is built without it)? If it is interesting enough to add to upcoming Git Rev News edition...

mjaix commented 7 years ago

Fixed a few typos, looking very much forward to see you in Brussels.

chriscool commented 7 years ago

@tfnico and @jnareb thanks for the links! @jnareb if a thread started as support, I think it is best to add it in the Support section. And yeah I think the thread you link to is interesting enough.

jnareb commented 7 years ago

@chriscool thread merged as pull request #218...

...and I am done.

chriscool commented 7 years ago

@jnareb thanks! I commented on the PR as I think there are a few typos/grammos that could be fixed. I didn't fixed them in the published edition but I think we should do that soon.

mjaix commented 7 years ago

@chriscool: I found only a very few tiny quirks in the the PR - plan to fix this part within the next 30 minutes.

mjaix commented 7 years ago

@chriscool Needed some time to understand the problem, and partially rewrote the PR #218 contribution to make it [hopefully] more understandable. Will make sure to edit markdown from a host with the tool chain established next time. @peff Thanks for providing regex insights.

mjaix commented 7 years ago

Plan to run mailchimp tomorrow afternoon/early evening if that is o.k. with you.

chriscool commented 7 years ago

@mjaix thanks for the improvements! Yeah, tomorrow afternoon/early evening is ok for me.

mjaix commented 7 years ago

Hi, after fixing yet another very tiny typo, I deliberately sent the mail, to get the News out of the door (Git merge is scheduled next week, isn't it?). A detail I found which I do not like at all is that the backquoted parts in markdown, which get a white background in the Github web, keep the normal background in MailChimp. Unfortunately, I don't have any time left this month to dig into this problem, but I think we should try to tackle it for the next edition. Recorded as issue #220.

chriscool commented 7 years ago

@mjaix thanks for sending the emails and for creating the issue! @jnareb are you going to the Git Merge too? It would be nice if we could all meet there and discuss about Git Rev News a bit.

jnareb commented 7 years ago

Unfortunately I won't be at Git Merge 2017.