Commits
- Commit:
a698f62e1bd91bd51649d4d59a2a1dbddf871d2b
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
allow 'got commit' while 'got histedit' is interrupted
- Commit:
30837e32b8c05d75e429f5587a658d6df7ddfda8
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
allow references to be passed to '-c commit' options
- Commit:
0ebf8283cd162a594e725ca2a1fd9f16e6ece6e4
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
initial 'got histedit' implementation
- 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:
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:
3ce1b84566a5dc6cbbfcfc87507aa84de4f0c9b9
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
initial 'got import' implementation
- Commit:
cd98404f2f7be2735f1190fefa76b86a54cec97c
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
clarify usage of 'got rebase' options in man page
- Commit:
723bd6d42a10339da0a65644962589f3dd03e459
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
clarify our intentions regarding clone/fetch and the master branch
- Commit:
7d7ffedbc869cda869d612f84b286ec60756661e
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
show how to create a commitable diff in got.1 EXAMPLES
- Commit:
ce33d90e1502875faf13bd2acd56bb06f5620a44
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
avoid cross-references to git-gc(1)
- Commit:
b48be8cf538bf50655557b4fe58d398f4d3934ee
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
update CAVEATS section in got.1
- Commit:
778a73c202451031815f6c71287901ff5ac448bb
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
fix wrong command listed in man page text
- Commit:
74d012d126797df0ab6a3cc0000568c3be981532
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
man page wording tweak
- Commit:
7acfb25b4c422de173d71a19a531ca4a19877f71
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
more clearly document the effect of 'got branch -d'
- Commit:
ba882ee388d95f88eb3e54d3ccd2b07e736e5190
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
make 'got branch -l' indicate work tree's current branch
- Commit:
86d25a1b02a67714850c0c7d78cfac065e455fe0
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
'got rm' -> 'got remove' in man page
- Commit:
f09e2405e1b95f1330287ea63b506140b0b65fbd
- From:
- Stefan Sperling <stsp@stsp.name>
- Date:
rebase man page tweaks