unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Colin Baxter <m43cap@yandex.com>
To: Richard Stallman <rms@gnu.org>
Cc: , "Paul W. Rankin" <pwr@sdf.org>, emacs-devel@gnu.org
Subject: Re: Extra files in fountain-mode ELPA package
Date: Thu, 29 Aug 2019 07:53:18 +0100	[thread overview]
Message-ID: <87mufsihsx.fsf@yandex.com> (raw)
In-Reply-To: <E1i3A5p-0006n7-IY@fencepost.gnu.org> (Richard Stallman's message of "Wed, 28 Aug 2019 22:23:21 -0400")

>>>>> Richard Stallman <rms@gnu.org> writes:

    > [[[ To any NSA and FBI agents reading my email: please consider
    > ]]] [[[ whether defending the US Constitution against all enemies,
    > ]]] [[[ foreign or domestic, requires you to follow Snowden's
    > example. ]]]

    >> Not sure how to answer some of these Q's, but GitHub Pages is
    >> just a static site generator/host, usually for project
    >> documentation websites.  All the info here:
    >> https://pages.github.com/

    > If you are using GitHub Pages, you surely know what job it does
    > for you.  Could you please describe the job?  I will look at that
    > site but the answer may not be obvious there.

    > What is the URL where you refer users who want to see the
    > documentation?  When users see the documentation, does the page
    > mention GitHub?

    > Can you please tell me the precise URL where users look at the
    > documentation?

Forgive me for butting in. The procedure for setting up a web-site at
github is essentially the following:- 

1. Set up github a/c with username as `user'.
2. The url for the repository will be `user.github.io'.
3. git clone https://github.com/user/user.github.io <RET>
4. cd /path/user.github.io <RET>
5. Write some html, css, etc. files.
6. git add, commit and push.
7. Visit https://user.github.io to see result.

Hope this help.

Best wishes,

-- 
Colin Baxter
www.Colin-Baxter.com
---------------------------------------------------------------------
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68  2A27 BBFA 2492 91F5 41C8
---------------------------------------------------------------------



  reply	other threads:[~2019-08-29  6:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27  6:53 Extra files in fountain-mode ELPA package Paul W. Rankin
2019-08-27 12:03 ` Stefan Monnier
2019-08-28  3:49   ` Paul W. Rankin
2019-08-27 23:24 ` Richard Stallman
2019-08-28  3:52   ` Paul W. Rankin
2019-08-29  2:23     ` Richard Stallman
2019-08-29  6:53       ` Colin Baxter [this message]
2019-09-02  2:15         ` Richard Stallman
2019-09-02  2:40           ` 조성빈
2019-09-06  6:12             ` 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=87mufsihsx.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=emacs-devel@gnu.org \
    --cc=pwr@sdf.org \
    --cc=rms@gnu.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.
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).