Darren J Moffat wrote:
Stephen Lau wrote:
Can you please give step by step instructions on exactly where we
need to rollback to, ie the revision/changeset number last known to
be good (or one close it it) would be really helpful.
It looks like the last common changeset was:
changeset: 1216:bbbeae705cee
user: masputra
date: Fri Jan 06 09:41:00 2006 -0800
summary: 6340735 write() may hang on loopback tcp connections
If you tell me which os.o project repositories you have and what
revision you want them brought up to - I can do that for you.
It isn't the ones on opensolaris.org I'm most concerned with it is the
ones currently sitting on my laptop and the ones on build machines in SWAN.
What is the sequence of hg commands I need to run to fix up my
repositories, keeping in mind they might well have changesets in them
that need to be preserved ?
Rich can correct me here if he knows a better way (he reassembled the
scm-migration/onnv-scm repository after the tree regeneration).
I believe the best thing to do would be to 'hg export' your changesets
you want to preserve, then move your current gate aside. Take a clone
of onnv-gate up to the last putback that happened before your started
your local changesets, then reimport (via 'hg import') your preserved
changesets back in.
I'm hoping Rich will chime in with the sequence of commands he used to
fixup onnv-scm... which will probably be more helpful to you.
cheers,
steve
--
stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net
opensolaris // solaris kernel development
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
