From: Robert Pluim <rpluim@gmail.com>
To: Mathias Dahl <mathias.dahl@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: [PATCH] Add abbrev suggestions
Date: Sat, 26 Sep 2020 16:19:04 +0200 [thread overview]
Message-ID: <m2lfgw1uzr.fsf@gmail.com> (raw)
In-Reply-To: <CABrcCQ6rp2+W80tpdOnOyKHMFhKZvXubBCfFj23--_Db=SGLyw@mail.gmail.com> (Mathias Dahl's message of "Fri, 25 Sep 2020 22:42:55 +0200")
>>>>> On Fri, 25 Sep 2020 22:42:55 +0200, Mathias Dahl <mathias.dahl@gmail.com> said:
>>
>> I have one more :-)
>>
Mathias> There's always more, isn't there... :-)
Mathias> If you have push access you can commit these changes yourself.
>>
Mathias> I thought about it initially, but I felt I might do more
Mathias> harm than good, despite having at least a decent
Mathias> understanding of Git nowadays. Seems I have an account
Mathias> with Savannah since, I have no idea when, perhaps I
Mathias> should give it a try. I need to read up on if there is
Mathias> any Emacs-specific Git flow though...
'CONTRIBUTE' discusses how to generate a patch with git that will be
easy to apply for an emacs committer without having to change
it. 'admin/notes/git-workflow' goes over the details of what to do if
youʼre committing yourself.
Robert
next prev parent reply other threads:[~2020-09-26 14:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 23:40 [PATCH] Add abbrev suggestions Mathias Dahl
2020-07-19 17:40 ` Mathias Dahl
2020-07-19 19:01 ` Eli Zaretskii
2020-07-25 8:12 ` Eli Zaretskii
2020-08-11 22:16 ` Mathias Dahl
2020-08-13 13:59 ` Eli Zaretskii
2020-08-13 14:29 ` Mathias Dahl
2020-09-14 22:04 ` Mathias Dahl
2020-09-15 6:20 ` Andreas Röhler
2020-09-18 8:39 ` Mathias Dahl
2020-09-15 8:16 ` Robert Pluim
2020-09-18 8:40 ` Mathias Dahl
2020-09-24 20:02 ` Mathias Dahl
2020-09-25 8:09 ` Robert Pluim
2020-09-25 20:42 ` Mathias Dahl
2020-09-26 14:19 ` Robert Pluim [this message]
2020-09-26 20:56 ` Mathias Dahl
2020-09-26 22:21 ` Stefan Monnier
2020-09-27 6:12 ` Eli Zaretskii
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2lfgw1uzr.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mathias.dahl@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.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).