git workflow draft

Stefan Majewsky stefan.majewsky at
Wed Feb 16 12:45:46 GMT 2011

On Tue, Feb 15, 2011 at 6:51 PM, Aaron J. Seigo <aseigo at> wrote:
> Only features / topics that are intended from the state to be merged with
> master should end up in the main repository, however. More experimental and/or
> long term efforts (an example presented was the kconfig refactor leading up to
> 4.0) should start in a personal clone, and when/if the work crosses the border
> into "this is realistically going to be merged with master" it can be moved
> into a branch in the main repository.

As far as I'm concerned, the only problem with such branch moves is
the potentially epic number of commit notification mails. If so, the
email hook should check if the push generates a new branch, and send
only one mail then, like "100 commits have been pushed into the new
branch foobar; see >>here<< for a complete log vs. master and >>here<<
for the diff".


More information about the kde-core-devel mailing list