IU had a problem with their virus scanner, and it held up a lot of SVN commit
(and possibly Trac) mails.
They just fixed the problem, and so we might see a bunch of SVN commit/Trac
mails trickle in over the next few hours.
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go t
Yeah - it looks like Jeff and/or Tim didn't authorize you yet.
On Feb 13, 2009, at 1:53 PM, Eugene Loh wrote:
Ralph Castain wrote:
Once you have them in the hg repo, you can do an "svn st" to see
if you need to do anything further before committing back to the
svn repo - e.g., add or re
Ralph Castain wrote:
Once you have them in the hg repo, you can do an "svn st" to see if
you need to do anything further before committing back to the svn
repo - e.g., add or remove files. When you are ready, just do an "svn
ci" to commit your changes to the svn repo.
Thanks, but I get:
When you push something to an hg repo, you have to go to that repo and
do an "hg up" to update it. Hg holds your changes until you do the
update.
Once you have them in the hg repo, you can do an "svn st" to see if
you need to do anything further before committing back to the svn repo
- e.
I'm having trouble figuring out how to put my changes back to the trunk.
I've been looking at the wiki pages, but don't really see the one last
piece that I need of this puzzle. I've used
https://svn.open-mpi.org/trac/ompi/wiki/UsingMercurial to get me through
these steps:
svn check-out of
