Re: Kernel SCM saga..
Linus wrote: It looks like an operation like "show me the history of mm/memory.c" will be pretty expensive using git. Yes. Per-file history is expensive in git, because if the way it is indexed. Things are indexed by tree and by changeset, and there are no per-file indexes. Although directory changes are tracked using change-sets, there seems to be no easy way to answer "give me the diff corresponding to the commit (change-set) object ". That will be really helpful to review the changes. Rajesh - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel SCM saga..
Linus wrote: It looks like an operation like show me the history of mm/memory.c will be pretty expensive using git. Yes. Per-file history is expensive in git, because if the way it is indexed. Things are indexed by tree and by changeset, and there are no per-file indexes. Although directory changes are tracked using change-sets, there seems to be no easy way to answer give me the diff corresponding to the commit (change-set) object sha1. That will be really helpful to review the changes. Rajesh - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
