From: Carsten Dominik <carsten.dominik@gmail.com>
To: Giovanni Ridolfi <giovanni.ridolfi@yahoo.it>
Cc: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] minor typos in Readme_maintainer
Date: Tue, 16 Nov 2010 15:17:27 +0100 [thread overview]
Message-ID: <6F794ACE-D4FF-4607-9811-9983F986BFC1@gmail.com> (raw)
In-Reply-To: <838w0t4lad.fsf@yahoo.it>
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
prev parent reply other threads:[~2010-11-16 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 10:26 [PATCH] minor typos in Readme_maintainer Giovanni Ridolfi
2010-11-16 14:17 ` Carsten Dominik [this message]
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=6F794ACE-D4FF-4607-9811-9983F986BFC1@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=giovanni.ridolfi@yahoo.it \
/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).