Bugzilla – Full Text Bug Listing
| Summary: | new repo page - no way to get git log of a remote | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Susan McCourt <susan> |
| Component: | Git | Assignee: | Project Inbox <orion.git-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | mamacdon |
| Version: | 0.4 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 369591 | ||
|
Description
Susan McCourt
I did a fetch on the remote at the time, but since the list of branches didn't change, I thought that it just didn't work. Szymon told me that you can click on the "see all branches" link to see all branches from all repos. That wasn't too obvious to me in this workflow (I'm trained from the old tree page to look for change underneath the repo vs. above, plus nothing changed.) Maybe just some kind of indicator near the "see all branches" link, could let me know that I something to make new branches available. I'm not suggesting a general mechanism for telling me there is new stuff on the server, just a way to help me so that if I caused a change in data from the page, it shows me where I need to go to see it. I'll suggest something here by 0.4. Actually at this point I think we can just consider this a dup of bug 373144. The symptom was a little different, but the solution is the same. If the remote tracking branch is visible on the repositories page by default, then it's easy to get to git log (this bug) and it's easy to do the fetch (bug 373144). *** This bug has been marked as a duplicate of bug 373144 *** |