Commits
- Commit:
f2b6a97d56d8273e6e97080c1b86b1dedd174ef7- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
allow branch names with tog log/blame/tree -c options
- Commit:
2312fc47a59d27ed181e1a095baf45c8b88cffd6- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
Xr tog.1 from got.1
- Commit:
a14c42fa1f4c86f703b4e1083d9c50b06e2d478a- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
whitespace
- Commit:
59d52b885b1715d5c3646ef027b4e571968b3771- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
the visual difference between a # comment and a root shell is subtle
- Commit:
c991308af6c56586d825c010c1bebdd8d0a8b6be- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
man page wording tweak for clarity
- Commit:
95fc3404b801bd9513878a56c019530d56c869d5- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
swap the order of two examples in man page
- Commit:
ac90e726bb38615ba5126584ccc9642a90e59a69- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
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.
- Commit:
37c06ea4bc43854ab1212229878ceceb14a26167- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
link _p versions of libraries if PROFILE=1; hint from claudio
- Commit:
00eb6a1fb9f2f7f11d18494a994d3594d5f495ef- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
get rid of an inline implementation of got_object_qid_free()
- Commit:
f35c2426d4c58783c933a6e27f798cbe3ee25c9a- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
make 'got rebase' close its commit graph when it is no longer needed
- Commit:
21a44f9829905ab96452436db7c39da4cc021315- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
document that 'got import' needs GOT_AUTHOR to be set
- Commit:
2930ef13eafda4afd5cdd96598b87af9379f904b- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
fix wrong path in EXAMPLES
- Commit:
f400486b3afe255f2c9f827c0c21c865e1f82b9b- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
some log -b documentation escaped the previous backout commit
- Commit:
cc54c5012c3c6f6ee05e749ef9f02331304b76df- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
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...
- Commit:
ea0bbcf85814cba68a68039e391ed8df51ea4a1e- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
fix idset_test build broken in 2256993b27260cd7860c34b47751dff21a7083a8