From: Carsten Dominik <dominik@science.uva.nl>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: feature request: org-patch command
Date: Sun, 26 Oct 2008 07:32:40 +0100 [thread overview]
Message-ID: <79697F3D-219C-4BA8-A667-3B6B43C2ED37@uva.nl> (raw)
In-Reply-To: <20524da70810252125n5c623ffeoe9114f80ee069c22@mail.gmail.com>
Hi Samuel,
it seems to me that people who want to create patches regularly would
live much better if they'd use a versioning system to create these
patches. What you describe is more a facility for the casual patch
producer, which are the people who usually don't write patches.
- Carsten
On Oct 26, 2008, at 5:25 AM, Samuel Wales wrote:
> To make it easier to patch correctly, perhaps it would help if you
> could visit an org file, and simply call an org-patch command that
> would do something like this:
>
> - create a directory as a sibling to the org source dir if it does
> not exist
> - put the original and a copy in it
> - remind the user to put it in load-path in front of org
> - let you edit the copy
> - give you hints on org coding style
> - remind you to use short functions that do only one thing
> - tell you how to instrument for testing
> - remind you of gnu requirements
> - tell you to run org-patch-diff to create a temporary buffer with
> the correct diff output
>
> At least, if I wanted to, say, correct a typo in an org function, I
> wouldn't bother unless I could do it this easily, for fear of getting
> it wrong.
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: 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:[~2008-10-26 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 4:25 feature request: org-patch command Samuel Wales
2008-10-26 4:29 ` Samuel Wales
2008-10-26 6:32 ` 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=79697F3D-219C-4BA8-A667-3B6B43C2ED37@uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@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).