git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Fwd: git p4: feature request - branch check filtering

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 22, 2014, 16:46 UTC
Message-ID
<xmqqoazt71nb.fsf@gitster.dls.corp.google.com>
In-Reply-To
<CADtnS+w9q0dmnGsZoDr12GZ-RSZzcfPs6rfii-4eK7Hhn2byag@mail.gmail.com>
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 ;-)
Previous: Dan PorterNext: Pete Wyckoff
Message 4 of 5 in “Fwd: git p4: feature request - branch check filtering”
  1. Dan PorterFeb 18, 2014
  2. Pete WyckoffFeb 23, 2014
  3. Dan PorterApr 22, 2014
  4. Junio C HamanoApr 22, 2014
  5. Pete WyckoffApr 23, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.