![]() ![]() ![]() ![]() Features should be small enough that you can make a small number of commits (ideally 1) before sending code out for review. Click Save to put your access change into effectīefore starting work on a feature, you should create a new git branch, assuming the code does not depend on anything outside of the main branch.Doing so would prevent graders from being able to see your repository and code changes. Do not enable the Exclusive option, as this prevents default permissions from being inherited.In the newly created Add group box, type your reviewer’s name, which will autocomplete to “user/Their Name (username)” and allow you to add.In the Reference: refs/* section, next to Add permission select Read, then click Add.In the web UI, go to Browse -> Repositories and select your repository.If you’ve created an individual repository (with only yourself as owner), then you’ll want to add access for select others to view/review your code: Only owners can read, create reviews, and submit code to repositories.Only site administrators (instructors, TA’s) can push directly to main and skip creating reviews. Owners can push code for review, but cannot push directly to the main branch without review.In all examples on this site, $ Access controlsīy default new repositories have the following access controls: I just wouldn't say that the protocol-space is a spectrum with TCP on one side and UDP on the other - there are many, many dimensions to look at.Our Gerrit Code Review site will serve as your main git repository, and will be your home for code reviews. That said, there are many non-tcp-non-udp protocols out there. I can't really see the benefit of this either. So now you have ACKs and NACKs and you essentially have TCP minus congestion control and where you don't bother to re-order packets based on seq #. if you're willing to wait forever, UDP is reliable in that you can never be sure you won't ever receive that packet). Reliable but unordered: for this to make sense you have to impose a timeout (i.e. No cheaper than UDP, and I can't really see a potential benefit over it. Unreliable but ordered: use UDP, enumerate your packets, and if you get a packet out of order, discard it. So then your question becomes: what about some properties and not others? There are ways around the fixedness of endpoints so I'll just look at reliability and ordered-ness. The notion of mostly ordered or mostly reliable we sort of get "for free" with UDP. All of those properties are binary things - it's either reliable or not reliable, ordered or not ordered, etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |