emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* [PATCH] minor typos in Readme_maintainer
@ 2010-11-16 10:26 Giovanni Ridolfi
  2010-11-16 14:17 ` Carsten Dominik
  0 siblings, 1 reply; 2+ messages in thread
From: Giovanni Ridolfi @ 2010-11-16 10:26 UTC (permalink / raw)
  To: emacs-orgmode Mode

[-- Attachment #1: Type: text/plain, Size: 75 bytes --]

the patch attached fixes few typos in Readme_maintainer

cheers,
Giovanni


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch --]
[-- Type: text/x-patch, Size: 1607 bytes --]

--- README_maintainer	2010-11-16 10:22:56.000000000 +0100
+++ README_maintainer-new.org	2010-11-16 11:17:40.677233600 +0100
@@ -62,5 +62,5 @@
 : pw update -s "Changed Requested" -m "What to change" NNN
 
-This will sand an email to the contributor and the mailing list with a
+This will send an email to the contributor and the mailing list with a
 request for changes.  The =-m= message should not be more than one
 sentence and describe the requested changes.  If you need to explain
@@ -83,5 +83,5 @@
 : pw merge -m "maintainer comment" NNN
 
-This will merge than patch into master, switch back to master and send
+This will merge the patch into master, switch back to master and send
 an email to both contributor and mailing list stating that this change
 has been accepted, along with the comment given in the =-m= message.
@@ -122,5 +122,5 @@
 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
+the master branch.  Since the bug 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
@@ -146,5 +146,5 @@
 This is still a significant headache.  Some hand work is needed here.
 
-Emacs uses bzr, and while I see all the advantages thiswould have, I
+Emacs uses bzr, and while I see all the advantages this would have, I
 cannot bring myself to switch away from git for my day-to-day work.
 So the way I have been doing things with Emacs is this:

[-- 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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH] minor typos in Readme_maintainer
  2010-11-16 10:26 [PATCH] minor typos in Readme_maintainer Giovanni Ridolfi
@ 2010-11-16 14:17 ` Carsten Dominik
  0 siblings, 0 replies; 2+ messages in thread
From: Carsten Dominik @ 2010-11-16 14:17 UTC (permalink / raw)
  To: Giovanni Ridolfi; +Cc: emacs-orgmode Mode

Thank you Giovanni.

- Carsten

On Nov 16, 2010, at 11:26 AM, Giovanni Ridolfi wrote:

> the patch attached fixes few typos in Readme_maintainer
>
> cheers,
> Giovanni
>
> --- README_maintainer	2010-11-16 10:22:56.000000000 +0100
> +++ README_maintainer-new.org	2010-11-16 11:17:40.677233600 +0100
> @@ -62,5 +62,5 @@
> : pw update -s "Changed Requested" -m "What to change" NNN
>
> -This will sand an email to the contributor and the mailing list  
> with a
> +This will send an email to the contributor and the mailing list  
> with a
> request for changes.  The =-m= message should not be more than one
> sentence and describe the requested changes.  If you need to explain
> @@ -83,5 +83,5 @@
> : pw merge -m "maintainer comment" NNN
>
> -This will merge than patch into master, switch back to master and  
> send
> +This will merge the patch into master, switch back to master and send
> an email to both contributor and mailing list stating that this change
> has been accepted, along with the comment given in the =-m= message.
> @@ -122,5 +122,5 @@
> 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
> +the master branch.  Since the bug 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
> @@ -146,5 +146,5 @@
> This is still a significant headache.  Some hand work is needed here.
>
> -Emacs uses bzr, and while I see all the advantages thiswould have, I
> +Emacs uses bzr, and while I see all the advantages this would have, I
> cannot bring myself to switch away from git for my day-to-day work.
> So the way I have been doing things with Emacs is this:
> _______________________________________________
> 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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-11-16 16:26 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-11-16 10:26 [PATCH] minor typos in Readme_maintainer Giovanni Ridolfi
2010-11-16 14:17 ` Carsten Dominik

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).