{"thread":{"id":"45576","subject":"[RFC PATCH] git-news: obtain latest news for your favorite VCS","startedAt":"2017-04-01T00:00:12Z","lastAt":"2017-04-01T20:12:58Z","messageCount":2,"participants":["Stefan Beller","Christian Couder"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"315968","messageId":"20170331235947.20010-1-sbeller@google.com","threadId":"45576","inReplyTo":null,"subject":"[RFC PATCH] git-news: obtain latest news for your favorite VCS","fromName":"Stefan Beller","fromEmail":"sbeller@google.com","sentAt":"2017-03-31T23:59:47Z","receivedAt":"2017-04-01T00:00:12Z","isPatch":true,"sender":{"key":"stefanbeller@gmail.com","avatar":"https://avatars.githubusercontent.com/u/455868?v=4"},"body":"Today when a user is interested in news regarding the Git, their favorite\nversion control, it is a challenging task to find out what is actually\nhappening.  If the user is using a Git in a distribution that packaged\nit nicely for them, they may find outdated information in their\ndistribution using the distributions choice of relaying news.\nAs Git is a fast paced project, this is not the desired behavior for\nmost users. They rather prefer the latest news.\n\nOne could argue that it is OK to expect the user to read the \"What's\ncooking\" emails or even release notes to get a grasp of the latest\ndevelopment of Git, but these news do not quite catch the lively\natmosphere of the mailing list with all its polite flame wars and\nopinionated arguments on why a patch is written the way it ends up in\nthe release notes.\n\nIt is time to fix the root case of this important user facing problem in\na sensible way that doesn't confuse the user.\n\nInvent a new sub command 'git-news', which presents the latest news\nin a way capturing all the interesting tid-bits of the mailing list as\nwell as the surrounding ecosystem.\n\nAs we're rushing the solution of this important problem, we did not\nconsider alternatives, such that we end up solving it in a backwards\ncompatible, but forwards incompatible way; clearly nobody in the future\nwants to add another command that points to different news source. This is\nwhy we can take the generic name 'git-news', instead of using the rather\nspecialized 'git-rev-news' command that is harder to remember and type.\n\nSigned-off-by: Stefan Beller <sbeller@google.com>\n---\n .gitignore            | 1 +\n Documentation/git.txt | 2 ++\n Makefile              | 1 +\n command-list.txt      | 1 +\n git-news.sh           | 4 ++++\n 5 files changed, 9 insertions(+)\n create mode 100755 git-news.sh\n\ndiff --git a/.gitignore b/.gitignore\nindex 833ef3b0b7..b2d9c1161f 100644\n--- a/.gitignore\n+++ b/.gitignore\n@@ -98,6 +98,7 @@\n /git-mktag\n /git-mktree\n /git-name-rev\n+/git-news\n /git-mv\n /git-notes\n /git-p4\ndiff --git a/Documentation/git.txt b/Documentation/git.txt\nindex ecc1bb4bd7..f4629aa39b 100644\n--- a/Documentation/git.txt\n+++ b/Documentation/git.txt\n@@ -35,6 +35,8 @@ manual page gives you an overview of the command-line command syntax.\n A formatted and hyperlinked copy of the latest Git documentation\n can be viewed at `https://git.github.io/htmldocs/git.html`.\n \n+A more entertaining section of news can be obtained via `git-news`.\n+\n ifdef::stalenotes[]\n [NOTE]\n ============\ndiff --git a/Makefile b/Makefile\nindex 9f8b35ad41..32e50f30a2 100644\n--- a/Makefile\n+++ b/Makefile\n@@ -519,6 +519,7 @@ SCRIPT_SH += git-merge-octopus.sh\n SCRIPT_SH += git-merge-one-file.sh\n SCRIPT_SH += git-merge-resolve.sh\n SCRIPT_SH += git-mergetool.sh\n+SCRIPT_SH += git-news.sh\n SCRIPT_SH += git-quiltimport.sh\n SCRIPT_SH += git-rebase.sh\n SCRIPT_SH += git-remote-testgit.sh\ndiff --git a/command-list.txt b/command-list.txt\nindex a1fad28fd8..150b287ada 100644\n--- a/command-list.txt\n+++ b/command-list.txt\n@@ -91,6 +91,7 @@ git-mktag                               plumbingmanipulators\n git-mktree                              plumbingmanipulators\n git-mv                                  mainporcelain           worktree\n git-name-rev                            plumbinginterrogators\n+git-news                                mainporcelain\n git-notes                               mainporcelain\n git-p4                                  foreignscminterface\n git-pack-objects                        plumbingmanipulators\ndiff --git a/git-news.sh b/git-news.sh\nnew file mode 100755\nindex 0000000000..1707dc633e\n--- /dev/null\n+++ b/git-news.sh\n@@ -0,0 +1,4 @@\n+#!/bin/sh\n+#\n+\n+/usr/bin/sensible-browser https://git.github.io/rev_news/\n-- \n2.12.2.576.g7be6e4ba40.dirty\n\n"},{"id":"316029","messageId":"CAP8UFD0Z7CRxbeKaJiks=uvGYsiYcXHMVHbCxzH7-A2+7Qf=Bg@mail.gmail.com","threadId":"45576","inReplyTo":"20170331235947.20010-1-sbeller@google.com","subject":"Re: [RFC PATCH] git-news: obtain latest news for your favorite VCS","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2017-04-01T20:12:50Z","receivedAt":"2017-04-01T20:12:58Z","isPatch":true,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Sat, Apr 1, 2017 at 1:59 AM, Stefan Beller <sbeller@google.com> wrote:\n\n[...]\n\n> diff --git a/git-news.sh b/git-news.sh\n> new file mode 100755\n> index 0000000000..1707dc633e\n> --- /dev/null\n> +++ b/git-news.sh\n> @@ -0,0 +1,4 @@\n> +#!/bin/sh\n> +#\n> +\n> +/usr/bin/sensible-browser https://git.github.io/rev_news/\n\nThanks for this entertaining patch :-)\n"}]}