From: Noorul Islam <noorul@noorul.com>
To: emacs-org list <emacs-orgmode@gnu.org>
Subject: [PATCH] Fix Typo in README_maintainer
Date: Fri, 15 Oct 2010 22:49:54 +0530 [thread overview]
Message-ID: <AANLkTikzZyi=YoQy5EAwFkGyhH6XX6w8c=tGjNz==mKc@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 67 bytes --]
Fix typo
* README_maintainer: Fix typo
Thanks and Regards
Noorul
[-- Attachment #2: README_maintainer.txt --]
[-- Type: text/plain, Size: 1553 bytes --]
diff --git a/README_maintainer b/README_maintainer
index 37d1494..5d1a67a 100644
--- a/README_maintainer
+++ b/README_maintainer
@@ -28,8 +28,8 @@ release. The release process is a single make command:
The release number for minor releases look like this: =7.13.01=
Minor releases are small amends to main releases. Usually they fix
-bugs discovered in a main release. The only yhe fix to the bug is
-bundled into a release, without the main development work going on on
+bugs discovered in a main release. Only the fix to the bug is
+bundled into a release, without the main development work going on in
the master branch. Since the big fix will also be needed in the
master branch, usually the fix is made in master and then
cherry-picked into maint. When this is done, a release is made from
@@ -41,7 +41,7 @@ maint with this command:
This is still a significant headache. Some hand work is needed here.
-Emacs uses bzr, I cannot bring myself to swith from git to bzr for the
+Emacs uses bzr, I cannot bring myself to switch from git to bzr for the
development version of Org-mode. So the way I have been doing things
is this:
@@ -56,7 +56,7 @@ is this:
2. When I have made a release (usually I wait for the minor releases
to stabilize), I copy org files into the Emacs repository. Yes, I
- do not merge, I copy. This has ben the source of some problems in
+ do not merge, I copy. This has been the source of some problems in
the past - but I have not had the patience to work out a better
mechanism.
[-- Attachment #3: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next reply other threads:[~2010-10-15 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-15 17:19 Noorul Islam [this message]
[not found] ` <4550FF5B-12AB-4275-9BD9-38D4755A7C14@gmail.com>
2010-10-17 3:17 ` [PATCH] Fix Typo in README_maintainer Noorul Islam
2010-10-17 5:36 ` Carsten Dominik
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='AANLkTikzZyi=YoQy5EAwFkGyhH6XX6w8c=tGjNz==mKc@mail.gmail.com' \
--to=noorul@noorul.com \
--cc=emacs-orgmode@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/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).