Re: git-cvsimport bug with dates

From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date: Nov 17, 2007, 10:12 UTC
Message-ID: <200711171112.23150.robin.rosenberg.lists@dewire.com>
In-Reply-To: <51419b2c0711160612r1a80bd5o686040f945e8d9c3@mail.gmail.com>

fredag 16 november 2007 skrev Elijah Newren:

Show 9 quoted lines

> On Nov 15, 2007 11:06 PM, Junio C Hamano <gitster@pobox.com> wrote:
> > When you use "branch@{date}" notation, you are not asking a
> > question on the project history, but a question on the local
> > view from _your_ repository on that project.
> 
> Interesting; that makes sense from a merge or pull viewpoint, but
> wouldn't it make more sense to have cvsimport ensure the commits are
> treated as though they actually existed in master as of the date
> specified in CVS?

Reflog do not work that way. They don't say when a commit entered a repo, only when a ref changed. For a CVS import things could work as you suggest but I think the confusion among newcomers would be massive if people start using reflogs 'as if' it said anyting about when a commit entered. It can be used as a hint.

Reflogs get pruned by git-gc and are not cloned (cannot be since they store local-only information.

Use the --since and --until switches instead.

-- robin