Marius via <[email protected]> writes: > Good evening, > > I'm interested in the proposals that are made on old issues 72457, 73202, > 68524 and 69343. The problem is that i get lost when reading them. > > Probably because my only experience with remote git repositories has been > with gitlab. For example in gitlab or similar web git helpers issues are > different entities than merge requests. Usually this means that the general > discussion of the topic is keep at the issue entity and those things related > with code and for example missing parentheses are keep at the merge requests > entity. > > On the other hand issues.guix.gnu.org treats issues and patches all in the > same thread which i find very confusing. > > For example if you add a commit message in a commit of your merge request you > would see that message in the main issue thread. In codeberg for example that > won't happen. > > But anyways that would change also between github/gitlab/codeberg etc. This > is no worries for me. > > What I want to know is how can work on that patch/merge. In gitlab for > example I would clone that merge request localy from the commit. > > For example from old 73202 how can I grab each patch part (small commit) into > my local repo? Because each patch message only contains the reference commit > and reference ID. I mean i could use each diff I guess in order to form my > local copy from that commit. But how to so that automatically? >
Hi Marius, A good way to do this is with mumi: guix shell mumi mumi current <issue number> mumi am mumi am is not very resilient in my experience so some more manual steps can be required like resetting to the base-commit mentionned in the cover letter. Otherwise, there is a patchworks instance you can use to access these issues as branches <https://patches.guix-patches.cbaines.net/project/guix-patches/list/> Lastly, the most manual option I know is to view the issue on debbugs.gnu.org and download as a mailbox, then use git am manually. > > Another thing that is not clear for me is how to keep track of issues/patches > that are related with the current issue/patch thread i'm working with. Do i > have to search the whole thread for mentions? > I don’t know. > If i want to make modifications to someone code should I apply a new patch to > the thread or that should only be performed by the one that started the > patches? > You can perfectly create a new version of a patch series if you are not the author. Especially if the issue has not been touched for a while. You can also ask the original author if they plan to finish it themselves. I think today it makes most sense to submit your new version as a codeberg PR and just send a message in the original issue to move the discussion to Codeberg. Hope that answers your questions, Noé > > It's probably a very natural way to use once you get used to it but in my > current situation I find it hard. > > Any help is useful. > > > Thank you. > > Best regards, > > Marius
signature.asc
Description: PGP signature
