Re: Request re git status

From: Duy Nguyen <pclouds@gmail.com>
Date: Feb 8, 2017, 06:13 UTC
Message-ID: <CACsJy8CWJvwSnmdpMg=atu+M8=4ksrTAYTgZyF5U7JnOCnPAkg@mail.gmail.com>
In-Reply-To: <CA+P7+xoZHOtURfbBbHHTpC3DsGxaGOVToqmW5wTg2EniRpL-Cg@mail.gmail.com>

On Wed, Feb 8, 2017 at 2:18 AM, Jacob Keller <jacob.keller@gmail.com> wrote:

Show 5 quoted lines

> Personally, I think that the fact that Git forces the user to think
> about it in terms of "oh I have to fetch" instead of that happening
> automatically, it helps teach the model to the user. If it happened in
> the background then the user might not be confronted with the
> distributed nature of the tool.

I agree. But I think there is some room for improvement. Do we know when the last fetch of the relevant upstream is? If we do, and if it's been "a while" (configurable), then we should make a note suggesting fetching again in git-status.

This is not exactly my own idea. Gentoo's portage (i.e. friends with apt-get, yum... if you're not familiar) also has this explicit "fetch" operation, which is called sync. If you haven't sync'd in a while and try to install new package, you get a friendly message (that helps me a couple times).

-- 
Duy