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 rxxxx
/* each commit log has a line like :
This commit was SVN rxxxxx
*/
and once you got (all) the git commits id of a given CMR, you can
cherry-pick them,
and push and issue the PR
/* i did not check whether cherry-pick automatically create/remove files */
Cheers,
Gilles
On 2014/10/03 0:51, Ralph Castain wrote:
> 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, and (b) apply it to my clone of ompi-release???
>
> 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.
>
>
> On Oct 2, 2014, at 3:41 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com>
> wrote:
>
>> 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
>> <gilles.gouaillar...@iferc.org> wrote:
>>
>>> 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 the reporter */
>>>
>>> what do you think ?
>>>
>>> Cheers,
>>>
>>> Gilles
>>>
>>> On 2014/10/02 19:24, Jeff Squyres (jsquyres) wrote:
>>>> 2. The following still-open CMRs were not brought over, and need to be
>>>> re-filed as pull requests:
>>>>
>>>> - https://svn.open-mpi.org/trac/ompi/ticket/4216: Nathan (BLOCKER)
>>>> - https://svn.open-mpi.org/trac/ompi/ticket/4816: Ralph
>>>> - https://svn.open-mpi.org/trac/ompi/ticket/4872: Ralph
>>>> - https://svn.open-mpi.org/trac/ompi/ticket/4888: Howard
>>>> - https://svn.open-mpi.org/trac/ompi/ticket/4900: Ralph
>>>> - https://svn.open-mpi.org/trac/ompi/ticket/4905: Mike Dubman
>>>> - https://svn.open-mpi.org/trac/ompi/ticket/4917: Jeff
>>>> - https://svn.open-mpi.org/trac/ompi/ticket/4911: Jeff
>>>> - https://svn.open-mpi.org/trac/ompi/ticket/4922: Jeff
>>>> - https://svn.open-mpi.org/trac/ompi/ticket/4923: Ralph
>>>> - https://svn.open-mpi.org/trac/ompi/ticket/4925: OMPI RM 1.8
>>>> - https://svn.open-mpi.org/trac/ompi/ticket/4926: Oscar
>>>> - https://svn.open-mpi.org/trac/ompi/ticket/4927: Jeff
>>> _______________________________________________
>>> devel mailing list
>>> de...@open-mpi.org
>>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>>> Link to this post:
>>> http://www.open-mpi.org/community/lists/devel/2014/10/15966.php
>>
>> --
>> Jeff Squyres
>> jsquy...@cisco.com
>> For corporate legal information go to:
>> http://www.cisco.com/web/about/doing_business/legal/cri/
>>
>> _______________________________________________
>> devel mailing list
>> de...@open-mpi.org
>> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
>> Link to this post:
>> http://www.open-mpi.org/community/lists/devel/2014/10/15967.php
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel
> Link to this post:
> http://www.open-mpi.org/community/lists/devel/2014/10/15971.php
