Re: Date-based limits

Daniel Barkalow [off-list ref] writes:

At some point, we might want to have a series of refs tracking changes to 
the user's heads over time.

Hmph.  If you really want something like that, I think you could
add a hook support for git-fetch to implement this as
automatically created lightweight tags, stashed in
$GIT_DIR/fetch-history/, deriving their names from the time of
the fetch; clone would grab everything below refs/ but this is
deliberately placed outside that hierarchy and won't get copied.
By definition, these point at commits reachable from some of
your heads (unless the remote repository maintainer is stupid
enough to rewind public trees ;-), so fsck-object would not see
them but it should not be a problem.

On Mon, 31 Oct 2005, Junio C Hamano wrote:

Daniel Barkalow [off-list ref] writes:

quoted

At some point, we might want to have a series of refs tracking changes to 
the user's heads over time.

Hmph.  If you really want something like that, I think you could
add a hook support for git-fetch to implement this as
automatically created lightweight tags...

Probably; I think this should also trigger on commits and such, and it 
would need a way for rev-list (or rev-parse?) to find the last one before 
a user-specified date, so that you don't have to figure out when the last 
change was that contributed to you seeing a particular tree on a given 
date.

	-Daniel
*This .sig left intentionally blank*