From: Junio C Hamano <gitster@pobox.com>
To: Philip Oakley <philipoakley@iee.org>
Cc: GitList <git@vger.kernel.org>,
Stefan Nwe <stefan.naewe@atlas-elektronik.com>
Subject: Re: [PATCH] Git release notes man page
Date: Tue, 18 Feb 2014 14:14:52 -0800 [thread overview]
Message-ID: <xmqqha7wcbkz.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1392460179-776-1-git-send-email-philipoakley@iee.org> (Philip Oakley's message of "Sat, 15 Feb 2014 10:29:38 +0000")
Philip Oakley <philipoakley@iee.org> writes:
> A few days too late for the 1.9.0 release cycle :(
>
> This responds to Stefan Nwe's request for a 'git help' command that would
> access the release notes. ($gmane/240595 17 Jan 2014).
>
> I've used the full name "release-notes" for the help guide rather than
> Stefan's original 'git help relnotes'.
>
> The release-notes man page lists just the notes for the current release.
> The combined notes for all releases is nearing 15k lines.
RelNotes are incremental and only useful for those who know what the
immediately previous release contained, but for most people who get
their Git from distros, I have this impression that the versions of
Git they get skip versions, and seeing the notable changes since the
previous source release will not give them wrong information---they
may have this warm fuzzy feeling that they know what is going on,
but they are missing information on all the accumulated changes that
were added in earlier versions their distro skipped---these changes
are still in the version they are running. I do not understand why
it is even a good idea to show release notes from the command line
"git" interface.
next prev parent reply other threads:[~2014-02-18 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-15 10:29 [PATCH] Git release notes man page Philip Oakley
2014-02-15 10:29 ` [PATCH] [PATCH] Provide a release-notes man page / guide Philip Oakley
2014-02-18 22:14 ` Junio C Hamano [this message]
2014-02-18 22:54 ` [PATCH] Git release notes man page Philip Oakley
2014-02-19 9:06 ` Stefan Näwe
2014-02-19 18:22 ` Junio C Hamano
2014-02-18 23:05 ` Junio C Hamano
Reply instructions:
You may reply publicly 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqha7wcbkz.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.org \
--cc=stefan.naewe@atlas-elektronik.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.