git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Request re git status

From
Jacob Keller <jacob.keller@gmail.com>
Date
Feb 8, 2017, 06:30 UTC
Message-ID
<CA+P7+xqg9b+49P6bO65E0q4a87BkNL76XGiUjcMg+UmDcU=WPg@mail.gmail.com>
In-Reply-To
<CACsJy8CWJvwSnmdpMg=atu+M8=4ksrTAYTgZyF5U7JnOCnPAkg@mail.gmail.com>
On Tue, Feb 7, 2017 at 10:13 PM, Duy Nguyen <pclouds@gmail.com> wrote:
Show 19 quoted lines
> On Wed, Feb 8, 2017 at 2:18 AM, Jacob Keller <jacob.keller@gmail.com> wrote:
>> 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
That seems reasonable.

Thanks, Jake

Previous: Duy NguyenNext: Samuel Lijin
Message 8 of 10 in “Request re git status”
  1. Ron PeroFeb 6, 2017
  2. Phil HordFeb 7, 2017
  3. Ron PeroFeb 7, 2017
  4. Konstantin KhomoutovFeb 7, 2017
  5. Samuel LijinFeb 7, 2017
  6. Jacob KellerFeb 7, 2017
  7. Duy NguyenFeb 8, 2017
  8. Jacob KellerFeb 8, 2017
  9. Samuel LijinFeb 8, 2017
  10. Cornelius WeigFeb 7, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.