![]() | |||||||||||||
Messages in this thread |
On Fri, Dec 20, 2002 at 06:59:46PM -0700, Justin T. Gibbs wrote: > Those were committed in separate changes into our local Perforce > repository, but I simply don't have the patience to replicate each > individual change in Perforce into a BK change. Since all of the > Linux universe likes stuff in BK format, I do what I can to accomodate > them. perforce can export unified diffs for each changeste-equivalent right? for the sgi ptools SCCS we use internally I wrote a simple script that extracts this diff, the commit message automates a BK checking with this. This makes my job of keeping mainline in sync a lot easier and preserves the fine granuality. And it works nicely although the internal tree has some additional noise in it (kdb and HSM support). > If it wasn't such a pain to get stuff into the tree, you would see > smaller changesets. Umm, getting smaller changesets in is not such a pain :) Linus has stated very often that he prefers small patches that do one thing and I 100% agree with him. Let me suggest we heel you out to get the current update in (and I think with your latest slave_* fixes and/or Doug's scsi_scan.c revamp it's time to get it in now) and you send small, self-contained patches afterwards? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:31 [from the cache] ©2003-2008 | |||||||||||||