On Fri, Nov 14, 2014 at 12:47 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Tue, 2014-11-11 at 00:15 -0800, Luis R. Rodriguez wrote: >> From: "Luis R. Rodriguez" <mcgrof@xxxxxxxx> >> >> When using backports against for packaging with --gitdebug you either >> have to use --clean or assume the directory is empty already. In either >> case you start fresh. With integration this will be a bit different, you >> could end up with a project directory where the git tree was present but >> only the target directory was empty. >> >> Calling git init on an already existing git directory will reinitialize >> your git tree, that can reset some config stuff, let's avoid that. > > I guess I don't care much, but it seems strange to me that you'd use > --gitdebug in this case, you'd end up committing crappy patches to the > top-level kernel tree? It was very useful to me when debugging, hence --gitdebug. Also, each step is actually what some folks may want to see done / committed as that may have been work done manually before for each kernel release bump, now its just automated. Luis -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
