Re: [PATCH] revision: introduce ref@{N..M} syntax.

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Linus Torvalds
Date: Sunday, December 17, 2006 - 11:14 am

On Sat, 16 Dec 2006, Junio C Hamano wrote:

Well, logically, if you do that, then you should also allow

	git log master@{one.week.ago..yesterday}

as a reflog expression.

"Because It Only Makes Sense(tm)".

		Linus

PS. Yeah, I'm only half serious. I like our revision parsing, and the 
above _would_ actually be consistent with the "master@{1..3}" kind of 
specification, but at the same time, it's also obviously more complex, and 
maybe it's not THAT usable.

But I think the "master@{date..date}" syntax would actually fall out 
automatically if you did the {x..y} parsing at a higher level and didn't 
force "x" and "y" to be digits only.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
What's cooking in git.git (topics), Junio C Hamano, (Sat Dec 16, 4:10 pm)
Re: What's cooking in git.git (topics), Brian Gernhardt, (Sat Dec 16, 9:35 pm)
Re: What's cooking in git.git (topics), Shawn Pearce, (Sat Dec 16, 9:42 pm)
[PATCH] revision: introduce ref@{N..M} syntax., Junio C Hamano, (Sat Dec 16, 11:46 pm)
Re: [PATCH] revision: introduce ref@{N..M} syntax., Linus Torvalds, (Sun Dec 17, 11:14 am)
Re: [PATCH] revision: introduce ref@{N..M} syntax., Junio C Hamano, (Sun Dec 17, 12:38 pm)
Re: What's cooking in git.git (topics), Andy Parkins, (Sun Dec 17, 4:41 pm)
[PATCH 1/2] add for_each_reflog_ent() iterator, Junio C Hamano, (Mon Dec 18, 2:40 am)