Any comment about upcoming Git Rev News edition 20 about git.github.io

[jnareb]

Yet another link: Deveo: List of equivalent commands in Git, Mercurial, and Subversion - not sure if worth including.

More links to come.

[chriscool]

Thanks @jnareb!

[chriscool]

Let's publish this edition next Wednesday October 19th.

By the way sorry but I managed to make a mistake in the commit message of: a955701
It's October 19th not October 20th.

[jnareb]

• Gittup is an entire(-ish) Linux distribution in git, where everything is built with tup, a file-based build system.

[jnareb]

• Lesser known Git commands article by Tim Pettersen... well, most of those are well named aliases using less known options or combination of options (push --force-with-lease, commit --amend --no-edit, stash --keep-index / --include-untracked / --all, status --short --branch, merge --no-ff,...)

[jnareb]

• GitHub Classroom as Textbook and Workbook by Rob Muhlestein on SkilStak blog

though this one might be too GitHub-specific.

[jnareb]

• Git – Basic hygiene of working with repository – The #AIMway (All In Mobile) by Jerzy Puchalski

I'm not sure if it was not present in previous Git Rev News...

Edit by @tfnico: Yup, this one was in the previous edition.

[jnareb]

Purposes, Concepts, Misfits, and a Redesign of Git would need, I think, something more that just link. There was short discussion on Git mailing list. And there was result of this work: Gitless.

[jnareb]

The "Git User's Survey 2016" is to end at 20 October 2016... one day after Git Rev News edition 20 - but I wouldn't have time to do the analysis anyway.

[jnareb]

• ripgrep is faster than {grep, ag, git grep, ucg, pt, sift} on Andrew Gallant's Blog; what's nice is (beside very comprehensive benchmark) explanation about how ripgrep is fast.

Maybe we could borrow some ideas for git grep / git log --grep / etc...?

[jnareb]

I don't know if patchwork, a web-based patch tracking system for OSS projects, was present in previous Git Rev News or not.

[jnareb]

• https://github.com/book/git-test-repository - Git repository full of special cases, for testing purposes

[chriscool]

I don't know if patchwork, a web-based patch tracking system for OSS projects, was present in previous Git Rev News or not.

@jnareb No it hasn't appeared on Git Rev News yet. Thanks!

[tfnico]

I'm working on adding the links now. Thanks for all the tips, @jnareb! I had some of them bookmarked already, but there were some new ones there too.

It would be cool if we had a "link pot" where everyone could easily add their own links, and easily check if it has been published or found earlier. I've been using diigo.com to collect the links personally, but unfortunately it starts to cost money when one wants to start more collaborative stuff.

[tfnico]

OK, links are in, @chriscool. Is it my turn to do the Mailchimp dance this time? :)

[chriscool]

@tfnico thanks for the links! And yeah it's your turn :-)

[jnareb]

I have submitted a few pull requests for 20th edition of Git Rev News: #193 , #194 and #195

[tfnico]

@jnareb I think the last two can be merged as well, but I'll wait for @chriscool since they're up in "his" part of the newsletter :)

[jnareb]

Wouldn't "Gerrit Summit 2016 is coming" link be better in (newly created) Events category?

[jnareb]

Yet another link:

• Why kernel development still uses email [LWN.net]

This is tangentially related, because:

• Linux kernel uses Git for development
• Git itself also uses email for its development

[tfnico]

@jnareb added. Thanks! If you keep this up we'll have to make you curator (interested?) :)

[jnareb]

Yet another pul request #196 (take it or leave it)

[jnareb]

@tfnico interested... though I cannot guarantee that I will have time for Git Rev News each month.

[chriscool]

@jnareb: great! No problem if you don't have time each month. We will you add you to the team in the next edition and maybe @peff can already give you commit rights to the repo in GitHub.

[peff]

and maybe @peff can already give you commit rights to the repo in GitHub.

Done.

[tfnico]

Nice! Welcome to the team, @jnareb!

[jnareb]

Yet another pull request: #197 (I'll start making use of commit bit for the next revision).

A question: how do you choose topics from git mailing list to be covered by Git Rev News?

[jnareb]

...and joined the team...

[tfnico]

MailChimp campaign has been sent! Note that there will be a problem some day with #198.

[chriscool]

Great, thanks!

[jnareb]

Should this issue be closed after Git Rev News 20?

[chriscool]

@jnareb people may find some problems in what we published so it might be better to not close it too early.

About the way I choose topics from the git mailing list, I think that the easiest and simplest for me is to write on a thread I found interesting when I read it. Sometimes I also choose topics that are involving many people and/or some specific people as I think it is nice to not always talk about the same contributors. I also like to talk about Git related talks at conferences especially the git merge.
Sometimes Junio or someone else points to a thread on one issue like the current one, and I think it could indeed be interesting for the current or the next edition.