I've usually been merging with onnv every Monday morning. I've yet to figure out how "hg history" correspond sto the "node" in the download page. After I do that, I'm thinking of creating a page on opensolaris with info about the phase 1 repository and a pointer to the closed-bins from the on download page.
Anurag James Carlson wrote: > Renee Danson writes: > >> On Wed, Aug 27, 2008 at 04:01:22PM -0400, James Carlson wrote: >> >>>> * How do we map the "node" identifier to the onnv bits the nwam gate >>>> is sync'd with? >>>> >>> They're listed by node ID on that page. ;-} >>> >> Right, I saw that when I looked at that page. My question was, based on >> the date of the to onnv, how do we know which node ID we need? I have no >> idea what that node ID means. >> > > "hg history" should tell you what you need to know. They're listed in > reverse order by date, so "latest" is almost always the one you want, > but if you need to, you can also use "hg tags" to get information > about the node IDs corresponding to particular builds (minus any > respins). > > >> Particularly if we need to simply point people to the right thing, we need >> to know which node ID to point them to. >> > > Use "hg history" to find out what you have. > > >> Okay. I'm just missing how we know which set of binaries to point them >> to. The "latest" set will only be correct for a very short time, right? >> > > Right ... though it varies. It's often good for at least a few days, > and then you'll need to specify a particular node. > > One way to simplify the problem is to merge only with known bi-weekly > builds, rather than just the repository of the moment. Those build > tags will always have node IDs that are in the list. > > >>> We can't have every project team wandering around in this forest. >>> >> Agreed. I'd love to know where to find a map. >> > > ;-} > >
