Any comment about upcoming Git Rev News edition 4

[git]

Any comment about upcoming Git Rev News edition 4

[chriscool]

I plan to publish this edition on the 3rd of May, so I pushed c7aa615.
Ideas about what to talk about are welcome.

[tfnico]

@chriscool You meant 3rd of June, I suppose :)

I would love a section about @rtyley's SubmitGit! I'll have a stab at it myself if I get around to it.

[chriscool]

@tfnico yeah 3rd of June of course, sorry! I will fix it...

[gitster]

While I like the idea of submitGit, I'd prefer to see a warning in the edition about overly excessive authorization it asks currently (which will be worked on soonish), until it gets fixed.

[edit] Roberto seems to have fixed it in the code (I do not know if the fix is already deployed)

[chriscool]

Actually it was June 3rd in the file. I messed up in the comment only.

[gitster]

Is it just me who finds "Support" a rather strange label? I do not offhand have a better suggestion, but most of the entries we saw so far were not "Help, I do not have a clue as to how to achieve X with Git". They were more like "I am observing this reality, that does not match my expectation".

Perhaps "Bugs & Non Bugs" ;-)

[gitster]

Ideas editors can pick and choose for topics in "Reviews" section:

• "git help" groups commands according to workflow
• allow fetching from a commit that is reachable from the tip.
• new tests for "git pull" by a GSoC student.
• a new configuration variable to specify CURLOPTSSLCIPHER_LIST.
• "cat-file --batch --follow-symlink".
• "git p4" spawning $P4EDITOR that specifies options (e.g. "emacs -nw").
• A short-hand branch@{push} that refers the last observed state of where we push the branch to.
• clean/smudge an empty contents bugfix, which lead to an enhancement to allow clean/smudge filters to quit before reading their input fully.
• Teach "git diff" and friends to optionally highlight whitespace errors on lines other than new ones.
• Update "refs" API to use opaque "struct object_id".
• More-porcelains-in-C GSoC student project ("git am").
• "git for-each-ref" GSoC student project (preliminary refactoring).
• "git send-email" to support the aliases file used by sendmail.
• "git submodule" documentation update (Stefan).
• Bring consistency to error reporting mechanism used in "refs" API.

Items for "Releases" section.

• 2.3.8 (final for 2.3.x series for now)
• 2.4.1 and 2.4.2
• Git for Windows 2.x preview

Items for "Discussions" section (which would be a better name to put the "Support" items)

• "git config" barfs, saying "Out of memory?" when you "mkdir $HOME/.gitconfig"
• Stefan Beller restarted another round of "Protocol version 2" discussion

[chriscool]

@gitster thanks for the suggestions, I will have a look at them.
About "Support", yeah it is perhaps not the best word, but for example I don't think that "Help" would be better and I don't have any other suggestion either.

[gitster]

@chriscool, @tfnico I updated the earlier comment on this issue to add a bit more review topics.

Also, I think s/Support/Discussions/ would be a good change.

[chriscool]

@gitster thanks for the topics you added. I won't be able to cover them all, but at least it gives me some choice :-)

About "Support", we already use "Discussions" as a header for the "Reviews", "Support" and "General" sections. ("General" was used for Git Merge talks.)

[rtyley]

While I like the idea of submitGit, I'd prefer to see a warning in the edition about overly excessive authorization it asks currently (which will be worked on soonish), until it gets fixed.

[edit] Roberto seems to have fixed it in the code (I do not know if the fix is already deployed)

Yep, the fix for this has been deployed with rtyley/submitgit#3 - incidentally, I'm using Prout on the project, so you can always easily see if a pull request has been released.

[gitster]

@chriscool These "potential topics" were dump of what I had, not necessarily all of them are interesting ones. Pick and choose freely, thanks.

Regarding "Support", throwing them into "General" category may be a better course of action than calling them "Support", then, I would think.

[chriscool]

@gitster if we are to have only "General" with a lot of different things in it and "Reviews", then I'd rather put everything under "Discussions" without any subsection. And that would annoy me as this news letter was created to promote people doing reviews and support and I would feel that we increase the risk of moving away from our original goal.

Your "Bugs & Non Bugs" is funny. I like it, but it feels a bit too limited. Maybe "Bugs & Features" or "Usability" or "User Experience"? "User Experience" is a bit a buzzword these days, but I think I like it anyway.

[chriscool]

@tfnico @rtyley @gitster I just added an article about submitGit.

[Mikachu]

At the bottom,

• git-multimail resurected! (written by Matthieu Moy)
  resurrected is spelled wrong, and it gets linked by markdown to something useless.

[gitster]

@chriscool @tfnico FYI, I've done a few updates for your review.

[tfnico]

Hi all, sorry for my absentness this week. I'll work on the releases and links sections tonight, FYI.

[chriscool]

@Mikachu thanks for the report. The problem is now fixed.

@gitster thanks I think everything you wrote is merged now.

[chriscool]

@tfnico no problem, thanks for merging Junio's articles and fixing everything.

[tfnico]

So, I'm done with my stuff (pushed everything yesterday).

The rest looks really nice, everyone! Thanks so much :)

[chriscool]

Let's close this as the edition has been published.