emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: applying patches
Date: Tue, 23 Aug 2022 10:43:35 +0800	[thread overview]
Message-ID: <87tu638yso.fsf@localhost> (raw)
In-Reply-To: <te06m9$26s$1@ciao.gmane.io>

Max Nikulin <manikulin@gmail.com> writes:

>> It might. It is probably even useful. Would you mind writing several
>> paragraphs for the manual about applying patches?
>
> It may be enough to add links to already written documents.

I'd say that the purpose of describing patch or git apply in the manual
is a quick reference for ordinary users who report a bug and want to
test the proposed fix.

More detailed instructions may be added to
https://orgmode.org/worg/org-contribute.html

> For those who are familiar with git:
>
> https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a-Project
>
> Perhaps I have seen better introduction how to use the "patch" command than
> https://www.gnu.org/software/diffutils/manual/html_node/Merging-with-patch.html

I'd better see these links in org-contribute.
Possibly, we can add a new item to "Ways that do not involve programming":
- Help to test the proposed patches: You can help checking the quality
  of existing patches submitted to the mailing list. Just apply the
  patch (see [[how to apply patches]]) and try using it with your Org
  setup. Then report any issues or rough edges.

<<how to apply patches>> can then detail different ways to do it and
provide the above links as further reading.

-- 
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92


      reply	other threads:[~2022-08-23  2:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12 12:40 Suspected bug: '#+STARTUP: indent' messes up inlinetasks' tag alignment Alain.Cochard
2022-08-13  6:33 ` Ihor Radchenko
2022-08-19 12:14   ` Alain.Cochard
2022-08-20  7:20     ` Ihor Radchenko
2022-08-21 15:13       ` Alain.Cochard
2022-08-22 12:08         ` Ihor Radchenko
2022-08-22 15:17           ` applying patches Max Nikulin
2022-08-23  2:43             ` Ihor Radchenko [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=87tu638yso.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@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).