Date-based limits (Was Re: GIT 0.99.9)
- From
Daniel Barkalow <barkalow@iabervon.org>
- Date
- Oct 31, 2005, 23:47 UTC
- Message-ID
- <Pine.LNX.4.64.0510311820060.25300@iabervon.org>
- In-Reply-To
- <Pine.LNX.4.64.0510301838110.27915@g5.osdl.org>
On Sun, 30 Oct 2005, Linus Torvalds wrote:
> (The danger with date-based things is that something may be 4 months old, > but it only got _merged_ yesterday, so it may be new to _you_. And the > --since="2 weeks ago" will not show it, which can be surprising to people > who expect things that are new to _them_ to be shown).
At some point, we might want to have a series of refs tracking changes to the user's heads over time. Then the right set of arguments could actually handle "what would I have seen on Thursday, when I hadn't pulled since Tuesday, and upstream got some changes on Wednesday that I got on Friday, and it's Saturday now." (That is, Wednesday's commits hadn't hit the local repository yet; the commit that we got to is dated Friday for local purposes, and the latest as of Thursday is dated Tuesday, which is the last time the ref file was modified.)
And we probably don't want to fetch or clone this stuff; I doubt most people want to know the history from somebody else's point of view. At least, I can't think of a use for it that wouldn't be better served by asking whoever for the hash out of their history.
-Daniel *This .sig left intentionally blank*