search

shilow / boar

Automatically exported from code.google.com/p/boar
https://bitbucket.org/mats_ekberg/boar/wiki/Home
0 stars 0 forks source link

Feature Requestion: boar diff #36

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
A diff command to be able to see the differences between revisions.

I know there has been discussion of issues with linked vs independent snapshot 
states with regard to efficiency trade offs. What are your thoughts on breaking 
up the single bloblist into separate components more along the lines of the git 
object model?

http://book.git-scm.com/1_the_git_object_model.html

I understand that simplicity is a guiding principal of boars design, but having 
separate per directory hashed "tree" objects can retain the same simple json 
format, but should allow a diff operation to run more efficiently by quickly 
surfacing only those directories that are dissimilar between revisions and 
allowing the script to quickly drill down to those differences. Just a thought.

Original issue reported on code.google.com by cryptob...@gmail.com on 19 Dec 2011 at 7:08

GoogleCodeExporter commented 8 years ago 
That should say "Feature Request*" ... not sure what a requestion is (a 
feature/questoin?) ;)

Original comment by cryptob...@gmail.com on 19 Dec 2011 at 7:11

GoogleCodeExporter commented 8 years ago 
A diff command to be able to see the changes between any two revisions sounds 
like a good idea. The command should however only report what files has 
changed, not show the data differences in individual files (as those files are 
assumed to be generic large binaries, boar cannot produce a diff in a 
meaningful way)

Regarding your comments on Git, I'm not sure it is obvious what approach is the 
fastest in any given situation.

Original comment by ekb...@gmail.com on 29 Dec 2011 at 2:36

GoogleCodeExporter commented 8 years ago 
This issue has been partially resolved. As of changeset a04fa646493c it is now 
possible to view the changes caused by a specific revision ("boar log -v -r 
<revision>"). What remains for this issue is to allow for viewing the changes 
between any two revisions.

Original comment by ekb...@gmail.com on 24 Jun 2012 at 11:52