On Sat, Feb 05, 2005 at 12:31:53AM +0100, Francois Romieu wrote: > Stelian Pop <[EMAIL PROTECTED]> : > [...] > > Now, suppose one of my patches introduced a problem. How can someone > > not using BK isolate the patch which introduced the problem ? All he > > can do is to back out the entire set of patches, and the whole point > > of having split the patch initialy into logical changes is lost. > > Nope: he digs the bk-commit mailing list archives. > > For example, from Roland's mail > 2005/01/31 01:37:39-05:00 len.brown > 2005/01/31 01:35:48-05:00 len.brown > 2005/01/31 00:15:20-05:00 len.brown > 2005/01/31 00:12:40-05:00 len.brown > [etc.] > > $ grep +/^ChangeSet.*2005/01/31.*len.brown ~/Mail/linux/bk-commit/200505 > ChangeSet 1.1983.5.2, 2005/01/31 00:15:20-05:00, [EMAIL PROTECTED] > ChangeSet 1.1938.498.11, 2005/01/31 00:12:40-05:00, [EMAIL PROTECTED] > ChangeSet 1.1983.5.3, 2005/01/31 01:37:39-05:00, [EMAIL PROTECTED] > ChangeSet 1.1938.498.12, 2005/01/31 01:35:48-05:00, [EMAIL PROTECTED] > > Same thing as in Roland's mail but the changes are isolated.
Interesting, I fergot about those commit mails, thanks for remining me. I think those emails could provide the missing piece of the puzzle and we could generate the missing branches based on them. Stelian. -- Stelian Pop <[EMAIL PROTECTED]> - 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/
