git@vger.kernel.org mailing list mirror (one of many)
 help / Atom feed
From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org
Cc: Stefan Beller <sbeller@google.com>
Subject: [RFC PATCH] git-news: obtain latest news for your favorite VCS
Date: Fri, 31 Mar 2017 16:59:47 -0700
Message-ID: <20170331235947.20010-1-sbeller@google.com> (raw)

Today when a user is interested in news regarding the Git, their favorite
version control, it is a challenging task to find out what is actually
happening.  If the user is using a Git in a distribution that packaged
it nicely for them, they may find outdated information in their
distribution using the distributions choice of relaying news.
As Git is a fast paced project, this is not the desired behavior for
most users. They rather prefer the latest news.

One could argue that it is OK to expect the user to read the "What's
cooking" emails or even release notes to get a grasp of the latest
development of Git, but these news do not quite catch the lively
atmosphere of the mailing list with all its polite flame wars and
opinionated arguments on why a patch is written the way it ends up in
the release notes.

It is time to fix the root case of this important user facing problem in
a sensible way that doesn't confuse the user.

Invent a new sub command 'git-news', which presents the latest news
in a way capturing all the interesting tid-bits of the mailing list as
well as the surrounding ecosystem.

As we're rushing the solution of this important problem, we did not
consider alternatives, such that we end up solving it in a backwards
compatible, but forwards incompatible way; clearly nobody in the future
wants to add another command that points to different news source. This is
why we can take the generic name 'git-news', instead of using the rather
specialized 'git-rev-news' command that is harder to remember and type.

Signed-off-by: Stefan Beller <sbeller@google.com>
---
 .gitignore            | 1 +
 Documentation/git.txt | 2 ++
 Makefile              | 1 +
 command-list.txt      | 1 +
 git-news.sh           | 4 ++++
 5 files changed, 9 insertions(+)
 create mode 100755 git-news.sh

diff --git a/.gitignore b/.gitignore
index 833ef3b0b7..b2d9c1161f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -98,6 +98,7 @@
 /git-mktag
 /git-mktree
 /git-name-rev
+/git-news
 /git-mv
 /git-notes
 /git-p4
diff --git a/Documentation/git.txt b/Documentation/git.txt
index ecc1bb4bd7..f4629aa39b 100644
--- a/Documentation/git.txt
+++ b/Documentation/git.txt
@@ -35,6 +35,8 @@ manual page gives you an overview of the command-line command syntax.
 A formatted and hyperlinked copy of the latest Git documentation
 can be viewed at `https://git.github.io/htmldocs/git.html`.
 
+A more entertaining section of news can be obtained via `git-news`.
+
 ifdef::stalenotes[]
 [NOTE]
 ============
diff --git a/Makefile b/Makefile
index 9f8b35ad41..32e50f30a2 100644
--- a/Makefile
+++ b/Makefile
@@ -519,6 +519,7 @@ SCRIPT_SH += git-merge-octopus.sh
 SCRIPT_SH += git-merge-one-file.sh
 SCRIPT_SH += git-merge-resolve.sh
 SCRIPT_SH += git-mergetool.sh
+SCRIPT_SH += git-news.sh
 SCRIPT_SH += git-quiltimport.sh
 SCRIPT_SH += git-rebase.sh
 SCRIPT_SH += git-remote-testgit.sh
diff --git a/command-list.txt b/command-list.txt
index a1fad28fd8..150b287ada 100644
--- a/command-list.txt
+++ b/command-list.txt
@@ -91,6 +91,7 @@ git-mktag                               plumbingmanipulators
 git-mktree                              plumbingmanipulators
 git-mv                                  mainporcelain           worktree
 git-name-rev                            plumbinginterrogators
+git-news                                mainporcelain
 git-notes                               mainporcelain
 git-p4                                  foreignscminterface
 git-pack-objects                        plumbingmanipulators
diff --git a/git-news.sh b/git-news.sh
new file mode 100755
index 0000000000..1707dc633e
--- /dev/null
+++ b/git-news.sh
@@ -0,0 +1,4 @@
+#!/bin/sh
+#
+
+/usr/bin/sensible-browser https://git.github.io/rev_news/
-- 
2.12.2.576.g7be6e4ba40.dirty


             reply index

Thread overview: 2+ messages in thread (expand / mbox.gz / Atom feed / [top])
2017-03-31 23:59 Stefan Beller [this message]
2017-04-01 20:12 ` Christian Couder

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply to all the recipients using the --to, --cc,
  and --in-reply-to switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170331235947.20010-1-sbeller@google.com \
    --to=sbeller@google.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

git@vger.kernel.org mailing list mirror (one of many)

Archives are clonable:
	git clone --mirror https://public-inbox.org/git
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.version-control.git
	nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
	nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
	nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
	nntp://news.gmane.org/gmane.comp.version-control.git

 note: .onion URLs require Tor: https://www.torproject.org/
       or Tor2web: https://www.tor2web.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox