From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>, Carlo Zancanaro <carlo@zancanaro.id.au>
Subject: Re: We need an RFC procedure [Re: Services can now have a default value]
Date: Sun, 23 Apr 2017 12:13:54 +0200 [thread overview]
Message-ID: <87wpabsa71.fsf@elephly.net> (raw)
In-Reply-To: <87pog4gihe.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> As for posting the change before applying it, I should do more of that.
> I’ve taken the bad habit of pushing what I consider as “simple” changes
> directly to the repo, but perhaps the criteria should be reconsidered.
> :-)
I think it’s fine to push simple changes directly. There hasn’t been a
single instance when you pushed something where I thought that it
shouldn’t have been pushed.
Between releases we are free to change things; they only have to be
mentioned in the ChangeLog for the next release. ABI breakage can get a
little annoying if one doesn’t know about it and the compilation fails
with unclear errors.
It’s a little unfortunate that packages are developed together with
everything else, because this means that there is no way for people to
opt out of breaking changes until the next release without also opting
out of getting any updates at all.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-04-23 10:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 22:51 Services can now have a default value Ludovic Courtès
2017-04-15 23:11 ` ng0
2017-04-17 11:56 ` Ricardo Wurmus
2017-04-19 23:22 ` ng0
2017-04-20 8:53 ` Ricardo Wurmus
2017-04-20 9:09 ` ng0
2017-04-23 10:23 ` Ricardo Wurmus
2017-04-17 11:58 ` Ricardo Wurmus
2017-04-19 14:42 ` Carlo Zancanaro
2017-04-19 15:18 ` ng0
2017-04-19 21:20 ` Ludovic Courtès
[not found] ` <8737d32abz.fsf@zancanaro.id.au>
2017-04-20 8:42 ` Ludovic Courtès
2017-04-20 10:19 ` Carlo Zancanaro
2017-04-21 22:04 ` Ludovic Courtès
2017-04-21 23:41 ` Carlo Zancanaro
2017-04-22 0:46 ` We need an RFC procedure [Re: Services can now have a default value] ng0
2017-04-22 7:12 ` Ricardo Wurmus
2017-04-22 10:08 ` ng0
2017-04-22 22:55 ` Ludovic Courtès
2017-04-23 10:13 ` Ricardo Wurmus [this message]
2017-04-23 12:02 ` ng0
2017-04-27 13:29 ` Ludovic Courtès
2017-04-27 16:37 ` Petter
2017-05-02 12:42 ` Ludovic Courtès
2017-05-22 21:23 ` Ricardo Wurmus
2017-05-22 22:45 ` Leo Famulari
2017-04-23 11:52 ` ng0
2017-05-13 10:39 ` Services can now have a default value Carlo Zancanaro
2017-05-13 22:53 ` Carlo Zancanaro
2017-05-15 12:48 ` Ludovic Courtès
2017-04-22 14:46 ` Christopher Allan Webber
2017-04-22 14:59 ` Jan Nieuwenhuizen
2017-04-22 22:57 ` Ludovic Courtès
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpabsa71.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=carlo@zancanaro.id.au \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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/guix.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).