|
2011-02-25
| ||
| 01:13 | • Fixed ticket [74cfdb438a]: `fs info FILENAME` appears to be broken plus 2 other changes artifact: 45eea7454b user: drh | |
| 01:13 | Clarify the documentation for the operation of the "info" command. Ticket [74cfdb438a246e46] check-in: 828bf98aff user: drh tags: trunk | |
|
2011-02-23
| ||
| 22:52 | • New ticket [74cfdb438a] `fs info FILENAME` appears to be broken. artifact: e193d0a85f user: anonymous | |
| Ticket Hash: | 74cfdb438a246e462a9a860dff858aa0f773a508 | ||
| Title: | `fs info FILENAME` appears to be broken | ||
| Status: | Fixed | Type: | Documentation |
| Severity: | Important | Priority: | |
| Subsystem: | Resolution: | Fixed | |
| Last Modified: |
2011-02-25 01:13:35 15.11 years ago |
Created: |
2011-02-23 22:52:49 15.11 years ago |
| Version Found In: | 4f78571eb2 | ||
| Description: | ||||
Pretty easy to reproduce this one.
% cd /tmp % mkdir bug-test % fs new fs-info-test.fossil % mkdir co % cd co % fs open ../fs-info-test.fossil % echo bar > foo.txt % fs add foo.txt ADDED foo.txt % fs ci -m "Add a test file" foo.txt New_Version: a152dde43c9bf3410205e98b7fee57555d92378a % fs info foo.txt fossil: no such object: foo.txt Exit 1 Getting in to feature request land that led to uncovering this bug. I was doing a vendor import of some code and started to apply a local patch to the new branch. I was hoping to be able to snag the contents of the patch from branch=trunk, but wasn't able to do so. While poking around to find an easy way to get the artifact-id from the command line, I stumbled across this bug not working. Ideally I'd like to be able to do something like: % fs finfo -p -r master some/path/foo.txt Without having looked at the code, it appears as though the arg to -r isn't performing a lookup of symbolic names. Associating artifact-ids with filenames would be ideal. Something like:
And have it spit out a list of artifacts that match a given file, or "-r tip" and have it only spit out the artifact-ids of what's in tip. | ||||