sebb> Not sure what you mean by that. I think the suggested flow is as follows:
1) "Clone Apache JMeter repository" $ git clone https://github.com/apache/jmeter.git This creates "jmeter" directory with "origin" pointing to "apache/jmeter.git" Then "git fetch" could be used to fetch updates from "apache/jmeter" repository 2) "Add side repository". It might be useful to track progress of a side branch. It might be useful to have "own" repository. $ git remote add vlsi https://github.com/vlsi/jmeter.git Then "git fetch vlsi" would fetch updates from vlsi/jmeter repository. It is exactly what I do, however I use "vs" name for my own repositories for brevity. "gitk --all" could be used to visualize current history (so origin/trunk represents current JMeter trunk, and vlsi/gradle represents my gradle branch) For now I have: $ git remote -v show origin https://github.com/apache/jmeter.git (fetch) origin https://github.com/apache/jmeter.git (push) vs https://github.com/vlsi/jmeter.git (fetch) vs https://github.com/vlsi/jmeter.git (push) 3) When we use Apache GitBox, committers would even have rights to update PRs by pushing to "other people's repositories". This is helps as sometimes it is much simpler for committer to update minor issues and update the branch to trigger CI rather than discuss that in comments. Vladimir
