From: Junio C Hamano <gitster@pobox.com>
To: Dan Porter <dpreid@gmail.com>
Cc: Pete Wyckoff <pw@padd.com>, git@vger.kernel.org
Subject: Re: Fwd: git p4: feature request - branch check filtering
Date: Tue, 22 Apr 2014 09:46:32 -0700 [thread overview]
Message-ID: <xmqqoazt71nb.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CADtnS+w9q0dmnGsZoDr12GZ-RSZzcfPs6rfii-4eK7Hhn2byag@mail.gmail.com> (Dan Porter's message of "Tue, 22 Apr 2014 10:29:19 +0100")
Dan Porter <dpreid@gmail.com> writes:
> I should have updated on this earlier, but I wished to refine my work
> on this feature before submitting. With 2.0 looming I'll submit
> what's there so far.
I am not Pete, but...
The pre-release time is to find and fix regressions that may have
been introduced since the last release while we tried to add new
features and fixes to 2.0 until now.
"With 2.0 looming" is not a good reason to send out a new work. In
fact, if 2.0 is "looming", it is already too late for the upcoming
release. Of course "With 2.0 looming" does not mean that you must
not work on things that are regression fixes---it is your own time
and effort, and it will be great if that can help later releases.
Thanks for contributing anyway ;-)
next prev parent reply other threads:[~2014-04-22 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADtnS+zWzPY6ftwxWUE+Gb-OKq_Kzf9y+fFfgJ-demWyX3azCg@mail.gmail.com>
2014-02-18 12:42 ` Fwd: git p4: feature request - branch check filtering Dan Porter
2014-02-23 15:12 ` Pete Wyckoff
2014-04-22 9:29 ` Dan Porter
2014-04-22 16:46 ` Junio C Hamano [this message]
2014-04-23 19:46 ` Pete Wyckoff
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=xmqqoazt71nb.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=dpreid@gmail.com \
--cc=git@vger.kernel.org \
--cc=pw@padd.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 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.