On Sat, 24 Nov, Bernd Paysan wrote:

> % fossil grep xyzzy ext1.txt
> 7c88a35016..cbaff03a91:ext1.txt:here we have the *xyzzy* string

I would be in favour of this approach for a version control system with
the concept of serial, incremental revision numbers where you can
deduce from a range N..M what all the revisions in between are.

However in case of hashes as revision "numbers", you cannot easily
- without invoking other commands to find out the timeline - deduce all
matching revisions. I'd rather vote for a "list all matching revisions"
in the --all case and the default behaviour to stop at the "most recent
match".

Greetings,
Stefan

-- 
Stefan Bellon
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to