unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Matthias Meulien <orontee@gmail.com>
Cc: monnier@iro.umontreal.ca, nferrier@ferrier.me.uk, emacs-devel@gnu.org
Subject: Re: ELPAing all the GNU manuals
Date: Mon, 29 Sep 2014 23:00:02 +0300	[thread overview]
Message-ID: <834mvqmc3h.fsf@gnu.org> (raw)
In-Reply-To: <1412019323.17937.3.camel@gmail.com>

> From: Matthias Meulien <orontee@gmail.com>
> Cc: monnier@iro.umontreal.ca, nferrier@ferrier.me.uk, emacs-devel@gnu.org
> Date: Mon, 29 Sep 2014 21:35:23 +0200
> 
> > Wrong, IME.  A Windows binary package either includes the docs or have
> > a "docs" package right near it.
> 
> My experience is that the info files that ship with Git for Windows
> don't cover all the GNU tools available in the Git bash console,
> starting with Bash.

What does that have to do with the issue at hand?  Users that have
Findutils etc. in the Git tree should not use them, they are for Git,
period.

If Windows users want to use Findutils etc., they should install MinGW
ports of those, which do come with docs.



  reply	other threads:[~2014-09-29 20:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-28  9:36 ELPAing all the GNU manuals Nic Ferrier
2014-09-28 10:47 ` Alan Mackenzie
2014-09-28 11:06   ` David Kastrup
2014-09-28 11:10     ` Nic Ferrier
2014-09-28 12:12       ` joakim
2014-09-28 12:41         ` David Kastrup
2014-09-28 12:48       ` Alan Mackenzie
2014-09-28 12:49 ` Eric Brown
2014-09-28 16:37 ` Stefan Monnier
2014-09-28 18:17   ` Nic Ferrier
2014-09-28 20:58     ` Glenn Morris
2014-09-29 10:32     ` Thomas Koch
2014-09-29 16:51       ` Nic Ferrier
2014-09-29 20:49       ` Richard Stallman
2014-09-29 12:34   ` Matthias Meulien
2014-09-29 13:25     ` Eli Zaretskii
2014-09-29 19:35       ` Matthias Meulien
2014-09-29 20:00         ` Eli Zaretskii [this message]
2014-09-29 20:47 ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=834mvqmc3h.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=nferrier@ferrier.me.uk \
    --cc=orontee@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).