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

Re: Fastest way to set files date and time to latest commit time of each one

From
Raymond E. Pasco <ray@ameretat.dev>
Date
Aug 29, 2020, 04:59 UTC
Message-ID
<C597RQ1V1DCG.3EEXY0665KK35@ziyou.local>
In-Reply-To
<xmqq8sdym93d.fsf@gitster.c.googlers.com>
On Fri Aug 28, 2020 at 11:20 PM EDT, Junio C Hamano wrote:
Show 7 quoted lines
> - The source of the rsync transfer is a git working tree. It often
> has the checkout of the latest and greatest version, but during
> development, it may switch to older commit (e.g. to find where
> regression occurred) or not-yet-ready commit (e.g. work in
> progress that is not given to upstream). You check out the
> version you want to sync to the destination before initiating
> rsync.

Assuming this is the case, perhaps a separate worktree that you touch less often being the source for rsync might save rsync some bandwidth/cpu checking things.

Previous: Junio C HamanoNext: Eric Wong
Message 3 of 6 in “Fastest way to set files date and time to latest commit time of each one”
  1. Ivan BaldoAug 29, 2020
  2. Junio C HamanoAug 29, 2020
  3. Raymond E. PascoAug 29, 2020
  4. Eric WongAug 29, 2020
  5. Ivan BaldoSep 2, 2020
  6. Andreas SchwabAug 29, 2020

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.