From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Philip Oakley <philipoakley@iee.org>
Cc: bin wu <idevcod@gmail.com>,
git@vger.kernel.org, git-for-windows@googlegroups.com
Subject: Re: Where can I find the MD5 or SHA1 of git preview client.
Date: Mon, 18 Apr 2016 08:17:27 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1604180812260.2967@virtualbox> (raw)
In-Reply-To: <4BBE5A41FFCB4B94816619143CED5FB5@PhilipOakley>
Hi Philip,
On Sun, 17 Apr 2016, Philip Oakley wrote:
> From: "bin wu" <idevcod@gmail.com>
> > There is still a question.Why not just post the the MD5 and SHA1 on
> > the download page?
> >
> I've created a page on the FAQ wiki
> https://github.com/git-for-windows/git/wiki/Release-Hashes
The only problem with that is that any GitHub user can edit them (and I do
not think that anybody apart from me monitors the wiki yet).
> PS the list prefers bottom posting, so that context is seen before the
> answers and comments.
Actually, bottom posting (i.e. quoting the entire mail wholesale, while
answering only specific parts of it) is also frowned upon. It shows a lack
of concern for the readers' time. Which in turn usually elicits a lack of
time for the writer's concern. :-)
The best idea is always to quote *only* the parts that you are responding
to, with just enough context to understand the discussion, and answering
inline. See for example: this mail.
Ciao,
Johannes
next prev parent reply other threads:[~2016-04-18 6:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-16 13:44 Where can I find the MD5 or SHA1 of git preview client bin wu
2016-04-16 15:19 ` Philip Oakley
2016-04-17 3:34 ` bin wu
2016-04-17 20:32 ` Philip Oakley
2016-04-18 6:17 ` Johannes Schindelin [this message]
2016-04-18 5:58 ` Johannes Schindelin
2016-04-18 12:50 ` Philip Oakley
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=alpine.DEB.2.20.1604180812260.2967@virtualbox \
--to=johannes.schindelin@gmx.de \
--cc=git-for-windows@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=idevcod@gmail.com \
--cc=philipoakley@iee.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).