Re: [orion-dev] "Recent commits on origin/master"

[Libing Wang <Libing_Wang@xxxxxxxxxx>]

The original design approach of the "mini logs" in the git status page was to show user the most recent 5 commits on both working and remote branches.
So they are lighter weight representations of git log on both remote and local mode. By this user is able to compare quickly and do merge if it is needed.
All of these convenience were based on one assumption: user has to fetch/merge manually by the commands provided by the UI(available from both git status and log).

I am not sure automatic fetching is good or not. To me, as a typical git user, if it fetches something automatically when I only go to the git status page, I will be really surprised. But it's just my personal feeling.
If we really want to do so, we may want to do it from git log navigator widget to make both mini and full versions of log consistent.
Plus, we also need to consider saving git credentials( https://bugs.eclipse.org/bugs/show_bug.cgi?id=359952) to make it silent.

-Libing


John J Barton ---11/21/2011 12:28:28 PM---On git/git-status.html the bottom half is labeled Recent commits on origin/master

From: John J Barton <johnjbarton@xxxxxxxxxxxxxxx>
To: Orion developer discussions <orion-dev@xxxxxxxxxxx>
Date: 11/21/2011 12:28 PM
Subject: [orion-dev] "Recent commits on origin/master"
Sent by: orion-dev-bounces@xxxxxxxxxxx

---

On git/git-status.html the bottom half is labeled

Recent commits on origin/master

I believe this title is not correct, or at least it is confusing. I
think of "origin/master" as the remote repo. The content in this
section a list of the local replica of origin/master (or so I imagine,
it's what |git fetch| updates).

But rather than changing the title, I suggest changing the content.
The vast majority of the time a dev will want to understand the remote
state, not the local replica of the remote state.  With the limited
git command set available through the UI, I'm unsure if we can do
anything with the local replica other than merge it. So between the
time we merge and the next time we look at the git status page, the
content in the bottom area is pointless. It only shows the log
messages we have already merged into our working branch. We can't
compare it to our commits because it's already out of date.

So a concrete suggestion: asynchronously issue git fetch and update
the bottom area 1) every time we update git status, 2) once every 5
minutes.

jjb
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev