No worries, just thought I'd mention it during this "training wheels" phase for
everyone's sake, not just yours. Besides, there was an obvious gap in the
docs. :)
-Dave
On Oct 8, 2014, at 9:42 AM, Howard Pritchard wrote:
> Hi David,
>
> Yes I know about this. I realized as soon as I did th
FWIW, I don't typically set "pull with rebase" to be my default. Here's why:
1. If/when I login to a new machine and start doing some OMPI work, if I "git
pull" and expect it to automatically rebase, I might get a nasty surprise if I
don't have the default "pull with rebase" behavior set up on
Hi David,
Yes I know about this. I realized as soon as I did the push that it was
pushing
the commits that I'd pulled on top of my changes back into the repo. ugh.
Jeff suggested the pull with rebase. I added that as default in my global
config file.
In the past I'd not hit this because the
On Oct 3, 2014, at 5:10 PM, git...@crest.iu.edu wrote:
> - Log -
> https://github.com/open-mpi/ompi/commit/93eba3ac70606db12465319804f2733f13bc9ca4
>
> commit 93eba3ac70606db12465319804f2733f13bc9ca4
> Merge: fd6a044 bd2974f
> Author
Jeff,
one last thing ...
could you please make sure you (since you have write access to
ompi-release) can assign an issue to me (since i do not have write
access to ompi-release *but* i am part of the open-mpi organization)
/* i think we already validated this on a sandbox, but i would like to
b
Jeff,
I addressed your comments and it is in the trunk for 2 weeks already. I
thought that you are in rush with hosting migration, so I didn't show up.
Current solution is not complete. I plan to return to it to implement
continuous synchronisation as I will have the timeframe. However it should
be
