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

Re: What's cooking in git.git (Jan 2013, #08; Tue, 22)

From
Chris Rorvick <chris@rorvick.com>
Date
Jan 23, 2013, 13:26 UTC
Message-ID
<CAEUsAPaUy5ug0_HPjWDTSnAG0kURhP-1-9nOu9_Tpn5nEv6N_Q@mail.gmail.com>
In-Reply-To
<20130123092858.GJ7498@serenity.lan>
On Wed, Jan 23, 2013 at 3:28 AM, John Keeping <john@keeping.me.uk> wrote:
Show 5 quoted lines
> In my opinion the incremental import support really is substantially
> worse in cvsimport-3 than cvsimport-2.  cvsimport-2 looks at the output
> of git-for-each-ref to calculate the dates from which to continue each
> branch.  cvsps cannot be told this information and so the cvsimport-3
> script just takes the date of the last commit on the current branch.

Do you really need a timestamp per branch, though? If you have branches A and B, and B has a commit timestamp 5 minutes after A, you can infer that nothing happened on A for those five minutes, right? So maybe a single timestamp is sufficient, it just may not be picking the right one. Instead cvsimport-3 should compute the latest timestamp across all import branches.

Chris
Previous: John KeepingNext: John Keeping
Message 5 of 15 in “What's cooking in git.git (Jan 2013, #08; Tue, 22)”
  1. Junio C HamanoJan 22, 2013
  2. John KeepingJan 22, 2013
  3. Junio C HamanoJan 23, 2013
  4. John KeepingJan 23, 2013
  5. Chris RorvickJan 23, 2013
  6. John KeepingJan 23, 2013
  7. Junio C HamanoJan 23, 2013
  8. John KeepingJan 23, 2013
  9. Junio C HamanoJan 24, 2013
  10. git-cvsimport.txt: cvsps-2 is deprecatedJohn Keeping, Jan 24, 2013
  11. Junio C HamanoJan 24, 2013
  12. John KeepingJan 24, 2013
  13. Junio C HamanoJan 24, 2013
  14. Chris RorvickJan 25, 2013
  15. John KeepingJan 25, 2013

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.