From: Stefan Beller <stefanbeller@googlemail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Remove deprecated OPTION_BOOLEAN
Date: Mon, 29 Jul 2013 20:04:21 +0200 [thread overview]
Message-ID: <51F6AEA5.7040504@googlemail.com> (raw)
In-Reply-To: <7vbo5l1c5a.fsf@alter.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
On 07/29/2013 07:58 PM, Junio C Hamano wrote:
> Stefan Beller <stefanbeller@googlemail.com> writes:
>
>> So recently Junio released -rc0. Is that a reason to not
>> send out patches, which do not do bugfixes? So the following
>> commit for example doesn't fix a bug nor does it add a feature.
>> Is it fine to send out such kind of commits during the -rc
>> times or better wait for the next development cycle?
>
> It would be a good idea to show it to others as a preview of what to
> come even in a pre-release freeze period, so that people holding
> real patches in the affected area can work with you to avoid
> conflicts.
>
> But I would not expect them to be applied to the upcoming release,
> nor even 'next'---this largely depends on the maintainer workload.
>
> Thanks.
>
Thanks for the answer. Let me rephrase the question a little bit:
Would you rather encourage to send it out now, or later?
("I'll apply it ot a local branch and eventually remember it next
release to merge." or "I'll forget about such stuff, you need to
resend it anyway.")
Regarding possible merge conflicts I'd be happy to resolve them
and not add a burden to people doing features.
Stefan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2013-07-29 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 15:38 [PATCH] Remove deprecated OPTION_BOOLEAN Stefan Beller
2013-07-29 15:38 ` Stefan Beller
2013-07-29 18:11 ` Junio C Hamano
2013-07-29 18:18 ` Stefan Beller
2013-07-29 17:58 ` Junio C Hamano
2013-07-29 18:04 ` Stefan Beller [this message]
2013-07-29 18:50 ` Junio C Hamano
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=51F6AEA5.7040504@googlemail.com \
--to=stefanbeller@googlemail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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 NNTP newsgroup(s).