| |||||||||||||
Lessons from PostgreSQL's Git transitionLessons from PostgreSQL's Git transitionPosted Oct 13, 2010 19:55 UTC (Wed) by dlang (✭ supporter ✭, #313)In reply to: Lessons from PostgreSQL's Git transition by petereisentraut Parent article: Lessons from PostgreSQL's Git transition
the git best practices method would be to have the work on this feature done in a separate branch.
the initial commit would be by author C (the prototype), with a follow-up patch(s) by author A, with credit to author B in the commit message or a comment in the code, a reviewed by: tag crediting author D (possibly in the merge commit), and an additional patch for the documentation by author E.
this then gets merged in and everyone can see what was done on this, these aren't mixed in with other commits for unrelated things (until after it's in the mainline, at which point fixes are going to be separate patches anyway)
(Log in to post comments)
|
|||||||||||||