From: Marcin Borkowski <mbork@mbork.pl>
To: John Wiegley <jwiegley@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Git and submitting patches to fix bugs
Date: Fri, 13 Nov 2015 18:48:32 +0100 [thread overview]
Message-ID: <87pozdoknj.fsf@mbork.pl> (raw)
In-Reply-To: <m2h9kp7vkw.fsf@Vulcan.attlocal.net>
On 2015-11-13, at 16:44, John Wiegley <jwiegley@gmail.com> wrote:
>>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Ideally, VC should have support for this, of course, in which case the Emacs
>> email setup will be used automatically.
>
> Even better, there's no reason we can't write something to automate all of
> this for future contributors. I.e.:
>
> 1. in your clone of Emacs, fix some stuff
> 2. commit
> 3. hit a key to submit your fix
> 4. get prompted with an issue number
> 5. done (assuming sendmail-send-it actually sends)
>
> I'll see what I can get done, unless someone else wants a hand at it.
>
> In general, it might be a good idea for us to have an Emacs module written
> just for Emacs development contributors, with commands to streamline our
> process.
This is a very good idea, though I'd prefer a Magit plugin/extension.
> Another command: You're in a Git repository for a project that's on ELPA; one
> key should be all you need to update your local clone of ELPA, and find
> yourself in a commit buffer to describe the update.
>
> John
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2015-11-13 17:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 0:38 Git and submitting patches to fix bugs John Wiegley
2015-11-13 8:12 ` Eli Zaretskii
2015-11-13 15:44 ` John Wiegley
2015-11-13 17:48 ` Marcin Borkowski [this message]
2015-11-13 22:03 ` Richard Stallman
2015-11-13 22:19 ` Marcin Borkowski
2015-11-14 21:06 ` Richard Stallman
2015-11-14 22:42 ` Marcin Borkowski
2015-11-14 23:36 ` John Wiegley
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pozdoknj.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.