From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Nic Ferrier <nferrier@ferrier.me.uk>
Cc: =?us-ascii?Q?=3D=3Fwindows-1252=3FQ=3FR=3DFCdiger=3F=3D?=
Sonderfeld <ruediger@c-plusplus.de>,
emacs-devel@gnu.org
Subject: Re: why do some programming modes have customize hooks and others do not?
Date: Mon, 20 Oct 2014 16:39:47 -0400 [thread overview]
Message-ID: <jwvppdm7a02.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87k33u5zey.fsf@ferrier.me.uk> (Nic Ferrier's message of "Mon, 20 Oct 2014 20:11:49 +0100")
>>> If I sent patches (once we're on git, how goes that?)
>> Same as for Bzr, yes.
> Not the same as for bzr, no. I don't have bzr and don't intend to
> install it.
You don't need to have Bzr to send patches, even though we currently
use Bzr. Same will hold for Git.
You do need Bzr if you want to commit patches yourself, OTOH.
> I'm happy to contribute on git though.
And once we've switched to Git (any day now), you'll need Git to commit
(which shouldn't be a problem for you, apparently).
> I think Artur had a good idea which I'd be happy to implement.
> Then it would be worth switching hook variables to customize.
It's worth a try, yes.
Stefan
prev parent reply other threads:[~2014-10-20 20:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 11:10 why do some programming modes have customize hooks and others do not? Nic Ferrier
2014-10-18 11:37 ` Bastien
2014-10-18 21:46 ` Stefan Monnier
2014-10-18 22:24 ` Nic Ferrier
2014-10-19 22:44 ` Rüdiger Sonderfeld
2014-10-20 2:15 ` Stefan Monnier
2014-10-20 8:17 ` Nic Ferrier
2014-10-20 10:38 ` Artur Malabarba
2014-10-20 10:54 ` Nic Ferrier
2014-10-20 12:07 ` Artur Malabarba
2014-10-20 16:47 ` Stefan Monnier
2014-10-20 18:29 ` Nic Ferrier
2014-10-20 16:02 ` Stefan Monnier
2014-10-20 19:11 ` Nic Ferrier
2014-10-20 20:39 ` Stefan Monnier [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.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=jwvppdm7a02.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=nferrier@ferrier.me.uk \
--cc=ruediger@c-plusplus.de \
/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).