Commits


clarify git's object garbage collection criteria a bit


allow branch names with tog log/blame/tree -c options


Xr tog.1 from got.1


whitespace


the visual difference between a # comment and a root shell is subtle


man page wording tweak for clarity


swap the order of two examples in man page


document how something like 'git reset @^' can be achieved Question from florian; One key difference to reset @^ is that the bad commit will remain in history. I suppose a future 'histedit' command could solve that.


link _p versions of libraries if PROFILE=1; hint from claudio


get rid of an inline implementation of got_object_qid_free()


make 'got rebase' close its commit graph when it is no longer needed


document that 'got import' needs GOT_AUTHOR to be set


fix wrong path in EXAMPLES


some log -b documentation escaped the previous backout commit


backout 499d7ecc534806c7daf8795b1c9f76575520921f It is better to use another option code for first-parent log. Having a -b option which takes no argument is too confusing. E.g. 'got log -b foo' would log the path 'foo', not branch 'foo' and I got confused by that myself already...


fix idset_test build broken in 2256993b27260cd7860c34b47751dff21a7083a8


make got-read-blob account for header len in size check Fixes "no space" error with blobs which happen to straddle the size boundary for in-memory handling.


plug a memory leak in got-read-blob


avoid dependency on delta.o in binaries which don't need it


initial 'got import' implementation


oops; several got commands were missing their pledge(2) calls


show xfail test result before running 'git fsck'


run 'git fsck' after every cmdline test


clarify usage of 'got rebase' options in man page


clarify our intentions regarding clone/fetch and the master branch