Jeff,
i could not find how to apply a label to a PR via the web interface (and
i am not sure i can even do that since authority might be required)
any idea (maybe a special keyword in the comment ...) ?
Cheers,
Gilles
On 2014/10/03 1:53, Jeff Squyres (jsquyres) wrote:
> On Oct 2, 2014, at 12:4
Ralph,
what about cherry-pick ?
the most painful part is probably to manually retrieve the git commit id
of a given svn commit id
git log master, and then search r
/* each commit log has a line like :
This commit was SVN rx
*/
and once you got (all) the git commits id of a given CMR, yo
On Oct 2, 2014, at 11:47 AM, Ralph Castain wrote:
>
> On Oct 2, 2014, at 9:43 AM, Jeff Squyres (jsquyres)
> wrote:
>
>> On Oct 2, 2014, at 12:37 PM, Ralph Castain wrote:
>>
>>> Sonow that I've fought thru and created a pull request, I find that I
>>> cannot assign it to anyone for revi
On Oct 2, 2014, at 12:47 PM, Ralph Castain wrote:
> How are they going to review it, given they don't have authority to do
> anything on that branch? Can they still comment? Can they reassign them when
> done?
Yes, they can comment.
The idea was that they would apply the "reviewed" label when
On Oct 2, 2014, at 9:43 AM, Jeff Squyres (jsquyres) wrote:
> On Oct 2, 2014, at 12:37 PM, Ralph Castain wrote:
>
>> Sonow that I've fought thru and created a pull request, I find that I
>> cannot assign it to anyone for review. The only users on the ompi-release
>> branch are myself and
On Oct 2, 2014, at 12:37 PM, Ralph Castain wrote:
> Sonow that I've fought thru and created a pull request, I find that I
> cannot assign it to anyone for review. The only users on the ompi-release
> branch are myself and Jeff (plus the ompiteam admin).
>
> So how do we assign someone to r
On Oct 2, 2014, at 9:37 AM, Jeff Squyres (jsquyres) wrote:
> On Oct 2, 2014, at 12:25 PM, Ralph Castain wrote:
>
>> No. Getting all the right patches (one at a time) from svn is slow,
>> and then it doesn't necessarily apply cleanly, so you go back to svn to
>> figure out what is mis
On Oct 2, 2014, at 12:25 PM, Ralph Castain wrote:
> No. Getting all the right patches (one at a time) from svn is slow,
> and then it doesn't necessarily apply cleanly, so you go back to svn to
> figure out what is missing, get another set of patches (one at a time), try
> again from s
Sonow that I've fought thru and created a pull request, I find that I
cannot assign it to anyone for review. The only users on the ompi-release
branch are myself and Jeff (plus the ompiteam admin).
So how do we assign someone to review it?
On Oct 2, 2014, at 9:25 AM, Ralph Castain wrote:
On Oct 2, 2014, at 9:21 AM, Jeff Squyres (jsquyres) wrote:
> On Oct 2, 2014, at 12:16 PM, Ralph Castain wrote:
>
>> FWIW: I've been trying that and it really, really doesn't work very well -
>> at least, not on the one I'm trying to do. People should expect this to be
>> extremely painful fo
On Oct 2, 2014, at 9:20 AM, Dave Goodell (dgoodell) wrote:
> On Oct 2, 2014, at 11:17 AM, Ralph Castain
> wrote:
>
>>
>> On Oct 2, 2014, at 9:13 AM, Dave Goodell (dgoodell)
>> wrote:
>>
>>> On Oct 2, 2014, at 10:38 AM, git...@crest.iu.edu wrote:
>>>
This is an automated email from th
On Oct 2, 2014, at 12:16 PM, Ralph Castain wrote:
> FWIW: I've been trying that and it really, really doesn't work very well - at
> least, not on the one I'm trying to do. People should expect this to be
> extremely painful for the transition.
Yes, I think people will have to be watch out for
On Oct 2, 2014, at 11:17 AM, Ralph Castain
wrote:
>
> On Oct 2, 2014, at 9:13 AM, Dave Goodell (dgoodell)
> wrote:
>
>> On Oct 2, 2014, at 10:38 AM, git...@crest.iu.edu wrote:
>>
>>> This is an automated email from the git hooks/post-receive script. It was
>>> generated because a ref change
On Oct 2, 2014, at 9:13 AM, Dave Goodell (dgoodell) wrote:
> On Oct 2, 2014, at 10:38 AM, git...@crest.iu.edu wrote:
>
>> This is an automated email from the git hooks/post-receive script. It was
>> generated because a ref change was pushed to the repository containing
>> the project "open-mpi/
On Oct 2, 2014, at 9:14 AM, Jeff Squyres (jsquyres) wrote:
> On Oct 2, 2014, at 11:51 AM, Ralph Castain wrote:
>
>> Do I just download the changeset(s) from Trac and patch them in? I guess
>> that will work if we don't have an alternative method.
>
> Yes, that's what I was planning to do for
On Oct 2, 2014, at 11:51 AM, Ralph Castain wrote:
> Do I just download the changeset(s) from Trac and patch them in? I guess that
> will work if we don't have an alternative method.
Yes, that's what I was planning to do for my CMRs (i.e., generate patches from
SVN and apply them git tree).
Pe
On Oct 2, 2014, at 10:38 AM, git...@crest.iu.edu wrote:
> This is an automated email from the git hooks/post-receive script. It was
> generated because a ref change was pushed to the repository containing
> the project "open-mpi/ompi".
>
> The branch, master has been updated
> via 3263f721
I agree that someone needs to do it. However, what isn't clear is *how* to do
it. I get the mechanics:
* clone the ompi-release 1.8 branch
* apply the required change
* issue a pull request
It's the second step that isn't clear. How the heck do I (a) find the change
that was originally applied,
Now that Open has migrated its repositories to GitHub, there is no point in
maintaining the read-only Bitbucket and GitHub mirrors of OMPI's SVN repository
any further. They are, respectively:
https://bitbucket.org/ompiteam/ompi-svn-mirror
https://github.com/open-mpi/ompi-svn-mirror
Un
According to Github, you haven't accepted your invitation yet:
[cid:34B7E99E-FBB8-4B2D-974A-6FAF2CC15E82@cisco.com]
On Oct 2, 2014, at 9:35 AM, Vasily Filipov
mailto:vas...@dev.mellanox.co.il>> wrote:
Hi Jeff,
I didn't get any "OMPI GitHub invite email ", I opened GitHub account
(vasilyMellan
Hi Jeff,
I didn't get any "OMPI GitHub invite email ", I opened GitHub account
(vasilyMellanox) and set a "Watch" state for :
https://github.com/open-mpi/ompi
https://github.com/open-mpi/ompi-release
Am I supposed to do something additional ?
Thank you,
Vasily.
On 02-Oct-14 13:24, Je
Fair enough.
*Someone* needs to re-file those CMRs as pull requests; probably in some cases
it's the reporter, probably in some cases it's the owner. :-)
On Oct 2, 2014, at 6:33 AM, Gilles Gouaillardet
wrote:
> Hi Jeff,
>
> thumbs up for the migration !
>
> the names here are the CMR owne
Hi Jeff,
thumbs up for the migration !
the names here are the CMR owners ('Owned by' field in TRAC)
should it be the duty of the creators ('Reported by' field in TRAC) to
re-create the CMR instead?
/* if not, and from a git log point of view, that means the commiter
will be the reviewer and not
(sorry for the delay in receiving this mail; there was a problem with the devel
mailing list last night, unrelated to the Github migration)
Short version
=
The Github conversion is complete. All OMPI activity is now at Github. Please
read the wiki, particularly the first few pages
24 matches
Mail list logo
