"Fred L. Drake, Jr." <fdrake@beopen.com> writes:
> Barry A. Warsaw writes:
> > I don't think that's true, because the file won't have the tag
> > information in it. That could be a problem in and of itself, but I
> > dunno.
>
> The confusion isn't from the tags, but the dates; if the ,v was
> created 2 years ago, asking for the python tree as of a year ago
> (using -D <date>) will include the file, even though it wasn't part of
> our repository then. Asking for a specific tag (using -r <tag>) will
> properly not include it unless there's a matching tag there.
Is it feasible to hack the dates in the ,v file so that it looks like
all the revisions happened between say
2000.08.19.10.50.00
and
2000.08.19.10.51.00
? This probably has problems too, but they will be more subtle...
Cheers,
M.
--
That's why the smartest companies use Common Lisp, but lie about it
so all their competitors think Lisp is slow and C++ is fast. (This
rumor has, however, gotten a little out of hand. :)
-- Erik Naggum, comp.lang.lisp
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4