I doint know how your going to support this as this will need to be done in gerrit master upstream and we are on 2.13 yet there are 2.14 and 2.15.

@Paladox: I don't see how the last comment is relevant. "this" in "this will need to be done" remains vague. Please be specific.

@Aklapper this task has the Google Code project. Which is suggesting that this is easy to implement and can run as soon as it is built.

We are running gerrit 2.13 with plans to update to 2.14. But because of the nature of this it depends on how easy this is to implement. Upstream wont allow any breaking changes or large changes on a stable branch. Does this require a plugin? Im not sure with the api in 2.13 if this can be supported until 2.14 / 2.15.

@Paladox , this is a git client tool, which interfaces with lots of different git servers. It can happily support them all. Please read tasks before you comment on them.

Oh sorry.

Im confused why was a task filled under the gerrit tag then? (im guessing it is so that the tool can support gerrit without gerrit needing any changes?)

(i read the task description before commenting this time)

/me removes Gerrit

Because it is a tool for Gerrit. *shrug* But removing the tag is ok.

https://codein.withgoogle.com/tasks/4815216372088832/

@Framawiki: This cannot be both a smaller Google-Code-in-2017 task and a larger Possible-Tech-Projects task.

So the PR is currently in review. Looks like you're doing good job @Phantom42 !

Thank you @Framawiki ! The pull request isn't merged yet, but as for progress report: we already have clone working and we also implemented patchset review and fetch.