On Wed, Jul 2, 2025 at 09:32 Jerry D <jvdelis...@gmail.com> wrote: > On 7/2/25 9:02 AM, Steve Kargl wrote: > > On Wed, Jul 02, 2025 at 04:36:38AM -0700, Damian Rouson wrote: > >> git branch > >> gir checkout > >> git add > >> git commit > >> git rebase > >> git push > >> > > The above IS the process everyone uses on gcc. The email is only a "pull > request" for reviewing the patches. It works quite well. Once it is > reviewed/approved, the requester does the last step which is the push. > > For this particular patch, 'save as' the file, "patch -p1 <thepatchfile > > This is great as long as one does it often enough to remember the command syntax, knows which directory to set as one’s present working directory, and the patch applies cleanly. Too often, these conditions aren’t true for me so I don’t bother trying anymore. However, if I knew that I could just pull a branch, I’d be a more frequent tester, which would be especially nice in the cases when the patch fixes a bug report that I submitted. Instead, because of the current process, I only test sometime after the patch has been approved and pushed a branch, which is pretty late in the game — especially if getting past one bug simply gets me far enough to expose another bug.
These two options aren’t mutually exclusive: if the person emailing a patch can also push their local branch to any public remote — presumably one under their GitHub account — then I’d pull the branch while others apply the patch. D > > There are others on the gcc team evaluating a platform, not GitHub, which > will > likely be integrated to generate an email review/approve request. It is > unlikely > the email will go away. I would expect multiple means of doing a "pull > request". > > > I don't use git other than 'git clone', 'git reset --hard', > > and 'git diff'. If gfortran development goes this route, > > I am done. > > > > -- > > steve > > Cheers, > > Jerry >
