emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Alan E. Davis" <lngndvs@gmail.com>
To: Manish <mailtomanish.sharma@gmail.com>
Cc: Carsten Dominik <dominik@uva.nl>, emacs-orgmode@gnu.org
Subject: Re: Re: Suggest changing git repo on website to refer to git protocol
Date: Thu, 24 Jul 2008 11:44:27 +1000	[thread overview]
Message-ID: <7bef1f890807231844u4f37012cg7e38971668f0956d@mail.gmail.com> (raw)
In-Reply-To: <e7cdbe30807231301t4d8bad3dq975193ac270eb884@mail.gmail.com>

On Thu, Jul 24, 2008 at 6:01 AM, Manish <mailtomanish.sharma@gmail.com> wrote:
>  On Wed, Jul 23, 2008 at 11:01 PM, Carsten Dominik wrote:
>  > Hi
>  >
>  > If a volunteer writes this up, I'd be happy to include it on the
>  > org-mode pages.
>
> I have just added "How do I keep current with Org mode developement?"
> to Org FAQ via Worg.  Request a review for language (English is not my
> first language.) and correctness (I am not sure if the links I added
> are alright.)
>
> -- Manish
>

I will gladly read and make suggestions, as far as that goes.

This seems the easy approach, and certainly sufficient: a mere mention
of this explanation on the Org-Mode page.

Alan

-- 
Alan Davis, Kagman High School, Saipan lngndvs@gmail.com

"It's never a matter of liking or disliking ..."
 ---Santa Ynez Chumash Medicine Man

"We have no art. We do everything as well as we can." ---Balinese saying

  reply	other threads:[~2008-07-24  1:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 16:48 Suggest changing git repo on website to refer to git protocol Denis Bueno
2008-07-22 16:54 ` Carsten Dominik
2008-07-22 17:00   ` Denis Bueno
2008-07-22 17:19   ` Ian Barton
2008-07-22 17:27     ` Carsten Dominik
2008-07-22 17:35       ` Denis Bueno
2008-07-22 17:54         ` Carsten Dominik
2008-07-22 20:01           ` Denis Bueno
2008-07-22 21:00             ` Manish
2008-07-23  2:22               ` Bernt Hansen
     [not found]                 ` <7bef1f890807230711y6e49b53emfd9027304d870a5c@mail.gmail.com>
2008-07-23 16:19                   ` Alan E. Davis
2008-07-23 17:01                     ` Manish
2008-07-23 20:19                       ` Dan Davison
2008-07-24  7:02                         ` Giovanni Ridolfi
2008-07-24 10:27                         ` Sebastian Rose
2008-07-23 17:31                     ` Carsten Dominik
2008-07-23 20:01                       ` Manish
2008-07-24  1:44                         ` Alan E. Davis [this message]
2008-07-24 18:24                         ` Manish
2008-07-24 18:26                           ` Carsten Dominik
2008-07-24 18:40                             ` Manish
2008-07-24 18:58                               ` Carsten Dominik
2008-07-26 11:07                                 ` Bastien
2008-07-26 13:39                                   ` Carsten Dominik
2008-07-25 18:35                               ` Carsten Dominik
2008-07-23 16:44                 ` Manish

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.orgmode.org/

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

  git send-email \
    --in-reply-to=7bef1f890807231844u4f37012cg7e38971668f0956d@mail.gmail.com \
    --to=lngndvs@gmail.com \
    --cc=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=mailtomanish.sharma@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/org-mode.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).