Thread: GitHub mirror
View Single Post
Old 01-15-2013, 05:59 PM   #12
kiwidude
calibre/Sigil Developer
kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.
 
Posts: 4,224
Karma: 1334002
Join Date: Oct 2010
Location: London, UK
Device: Kindle Paperwhite 3G, iPad 3, iPad Air
But how can you differentiate the two? A patch is generated based on differences against a base. As Kovid isn't managing your mirror, he has zero control or knowledge of what "base" the patch is generated against. For all he knows that patch is generated for code that was mirrored three months ago and no longer applies. At least when the contributor is on the same source control system they can be sure to easily sync to the main development trunk before generating their patch, or branch with confidence from it.

Also for major contributors they tend to work on a branch which Kovid merges in, which isn't an option when on another source system.

Last edited by kiwidude; 01-15-2013 at 06:01 PM.
kiwidude is offline   Reply With Quote