You can do whatever you want in your repo without fear of stepping on someone else's toes. The range of tags should then promptly be turned into a patch file, which would be the definitive representation of the patch and which would be tested by the buildbot, commented on or downloaded by other coders (particularly the ones who are not Git users) and eventually applied and committed by the project maintainer upon final acceptance. We also need a display to see if we have a clean merge between the project's branch and the personal branch.Ī simpler alternative is simply to have the user submit a range from one tag to another as part of the post in the issue queue. We would need to take care here that at the time of the post, branch refers to one commit, but at the time of the merge, branch could refer to more commits we don't really want because they're potentially unreviewed.
To merge the changes of the patch, the project maintainers could click on a link called 'merge' which would in turn merge all the commits from the personal branch into the corresponding branch of the project. The posted comment then allows downloading the patch, viewing the selected branch and it needs to contain the commit id. For the latter, she would select the branch which contains the commits which should turn into a patch. When posting to an issue in the project, she can decide whether she wants to just comment, attach a patch (as usual), or get a patch from her personal repo. One repository per project, per userĮach user gets a clone of the main repo hosted on d.o where she can do whatever she wants to.
#Github upstream smartgit how to#
What we haven't decided on is how to do that, there are several ways. This means, that somehow, we want to be able that, for a given project and a given issue all users which have submitted a ssh key can contribute. We all agree that we want some sort of github-like fork/clone to participate in a project with git.
0 kommentar(er)
