git - Can I generate patch off private commit and send it to maintainer? -
in progit says:
if want git try bit more intelligently resolve conflict, can pass -3 option it, makes git attempt three-way merge. option isn’t on default because doesn’t work if commit patch says based on isn’t in repository. if have commit — if patch based on public commit — -3 option smarter applying conflicting patch:
and
the other advantage of approach history of commits well. although may have legitimate merge issues, know in history work based; proper three-way merge default rather having supply -3 , hope patch generated off public commit have access.
so mean can base patch on private commit? wonder sense make lead obvious conflicts while merging because files in commit patch based on on contributor's side differ how files now, how can incorporate them? these things described in progit project maintainer's point of view it's not case contributor base patch on development secret branch.
a change can based off private commit, , apply long changes nonconflicting.
consider:
a master \--------b-----c head a upstream (public) master; b , c commits private branch. can generate patch b c , if a..b , b..c nonconflicting apply upstream public commit a.
the more polite thing reorder commits:
a master \--------c-----b head and submit patch a..c. if isn't possible (say, because intermediate stage commits have been published locally) should able cherry-pick commits branch dedicated preparing patches upstream submission:
a master \--------b-----c head \--------c' upstream-request
Comments
Post a Comment