[hwloc-devel] Create success (hwloc git dev-5-gb33642e)
Creating nightly hwloc snapshot git tarball was a success. Snapshot: hwloc dev-5-gb33642e Start time: Thu Oct 3 22:27:02 EDT 2013 End time: Thu Oct 3 22:29:28 EDT 2013 Your friendly daemon, Cyrador
[hwloc-devel] github hwloc repo reset
I chatted w/ Brice in IM: the github/open-mpi/hwloc repo ***has been completely reset*** and now reflects all the correct information. If you have any clones of the original githib/open-mpi/hwloc repo, either be *exceedingly* careful in pulling down new stuff, or, probably simpler/better: just rm -rf your local clone and pull down a fresh one. Big apologies to everyone for all this hassle; it was my mistake that caused this kerfuffle (bonus to everyone: use kerfuffle in a sentence today). -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [hwloc-devel] New git repo attempt
On Oct 3, 2013, at 12:31 PM, Brice Goglinwrote: > The master branch looks good to me, and the list of branches looks fine too. Good. > v1.7 misses the last git commits, but I guess you didn't update it yet. Yes; I replayed on the master, but not v1.7 yet. I'll go do that now... -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [hwloc-devel] New git repo attempt
Le 03/10/2013 18:07, Jeff Squyres (jsquyres) a écrit : > I did the conversion again, and then added the commits that we've put on > github since the original conversion (but I squashed most of them). I put > the resulting repo here: > > https://github.com/jsquyres/hwloc-convert-again > > Does this look ok to everyone? If so, I can kill the existing > githib/open-mpi/hwloc and replace it with this one. > The master branch looks good to me, and the list of branches looks fine too. v1.7 misses the last git commits, but I guess you didn't update it yet. Brice
[hwloc-devel] New git repo attempt
I did the conversion again, and then added the commits that we've put on github since the original conversion (but I squashed most of them). I put the resulting repo here: https://github.com/jsquyres/hwloc-convert-again Does this look ok to everyone? If so, I can kill the existing githib/open-mpi/hwloc and replace it with this one. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [hwloc-devel] nightly snapshot tarballs now available
Samuel Thibault, le Thu 03 Oct 2013 18:01:25 +0200, a écrit : > I have automatically imported the previous debian uploads. I don't > think we really need to keep the detailed commit, the releases have > brought small diffs enough. And that permits to switch to another layout which is nicer to handle with git-buildpackage. Samuel
Re: [hwloc-devel] nightly snapshot tarballs now available
Jeff Squyres (jsquyres), le Thu 03 Oct 2013 12:38:05 +0200, a écrit : > On Oct 2, 2013, at 12:47 PM, Brice Goglinwrote: > > I can do it (assuming the "hwloc-svn-conversion" git tree it uptodate). > > But I need somebody to create the ompi/hwloc-debian repo on github and > > give us credentials. > > Done. I have automatically imported the previous debian uploads. I don't think we really need to keep the detailed commit, the releases have brought small diffs enough. Samuel
Re: [hwloc-devel] nightly snapshot tarballs now available
On Oct 3, 2013, at 6:41 AM, Brice Goglinwrote: > It was likely moved to the attic. If svn2git doesn't find it, that's > fine, I still have it in my archives in case we ever want it (very > unlikely). Ah, ok. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
Re: [hwloc-devel] nightly snapshot tarballs now available
Le 03/10/2013 12:37, Jeff Squyres (jsquyres) a écrit : >> The only important one is "cuda". >> Most other branches were merged, or manually applied to trunk, or are >> obsolete. Maybe just keep "json" and "valarray" in case we ever need to >> revive them. > I just sent a mail to Dave; let's see what he says. > > I don't see a valarray branch in SVN -- where is that? It was likely moved to the attic. If svn2git doesn't find it, that's fine, I still have it in my archives in case we ever want it (very unlikely). Brice
Re: [hwloc-devel] nightly snapshot tarballs now available
On Oct 2, 2013, at 12:47 PM, Brice Goglinwrote: > I can do it (assuming the "hwloc-svn-conversion" git tree it uptodate). > But I need somebody to create the ompi/hwloc-debian repo on github and > give us credentials. Done. > The only important one is "cuda". > Most other branches were merged, or manually applied to trunk, or are > obsolete. Maybe just keep "json" and "valarray" in case we ever need to > revive them. I just sent a mail to Dave; let's see what he says. I don't see a valarray branch in SVN -- where is that? > Looks like we're also missing stable branches v0.9, v1.0 and v1.1 for > some reason. #$@%@#%$#@$% I'm re-running the svn->git conversion on my laptop to see if I can figure out why these branches didn't make it over. In the worst case, we can re-seed the hwloc git repo because nothing tremendously important has happened since the conversion (we can just replay the script update commits -- it'll be a little painful, but do-able). -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/