Thread (4 messages) flat view 4 messages, 3 authors, 2016-06-15

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

From: Chris Rorvick <hidden>
Date: 2016-06-15 22:55:52

Possibly related (same subject, not in this thread)

On Wed, Jan 23, 2013 at 3:28 AM, John Keeping [off-list ref] wrote:
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help