> -----Original Message----- > From: Sergei Shtylyov [mailto:[EMAIL PROTECTED] > Wessel, Jason wrote: > > Are there any other locations that have newer patches? > > No.
Given that you know of no more recent source archive than I do, which source repository did you want to start from, or did you have a patch tree against a recent kernel that you wanted to start with instead? I have several starting points which can be used to go forward to the mainline rc candidates. Presently I was using the linux2_6_21_uprev branch. Or I can take the git archive that Tom started and merge into the uprev branch as well. As an example: http://kgdb.cvs.sourceforge.net/kgdb/kgdb-2/?pathrev=linux2_6_21_uprev > > > In terms of the location for the source control, would you prefer > > kernel.org git to start with, > > You mean creating another one? Yes, I mean creating something new, because at this point we have diverged sets of sources and this will be the best means of consolidating everything into one stream of patches to be contributed to the mainline. > > > or updating the CVS patches in the kgdb.sourceforge.net? > > Well, to me patchset being kept under CVS (or git) control > looks the best for now. > Do you mean to use git in this way or in its usual way -- to > just commit the patches to it as they arrive (and ending up > with a longer patch stream)? If we use the git, there would be a much longer patch stream because the commits would accumulate, and I am ok with that. It is easy enough to consolidate changes into a logical set after there is stability. Jason. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Kgdb-bugreport mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
