Documentation | user/start: update gsoc guidance to remove MR submission (!150)

[Gedare Bloom (@gedare)]

Gedare Bloom commented on a discussion on user/start/gsoc.rst: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/150#note_119999

 > +  git format-patch HEAD^ -o ../
 > +
 > +This should create a file in the parent directory (``../``) with a filename
 > +like ``0001-commit-message.patch`` where the first (subject) line of your
 > +commit message gets embedded in the filename. You can just attach these files
 > +to a :r:url:`discord` message in the ``#gsoc`` channel.
 > +
 >  
 >  Creating and Sending Merge Requests
 >  -----------------------------------
 >  
 > -Before sending an MR, make sure that the changes you have made conforms to
 > -RTEMS coding standards.
 > -You can refer to :ref:`Contributing` section for instruction on creating and
 > -sending merge requests.
 > +Instead of passing around patches, we use merge requests (MRs) in gitlab to

fixed

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/docs/rtems-docs/-/merge_requests/150#note_119999
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20250214/2ab4a456/attachment-0001.htm>