Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Introduce cl_assert_equal_oid | Edward Thomson | 2014-07-01 | 1 | -1/+1 |
| | |||||
* | refs: remove the _with_log differentiation | Carlos Martín Nieto | 2014-01-15 | 1 | -1/+1 |
| | | | | | | Any well-behaved program should write a descriptive message to the reflog whenever it updates a reference. Let's make this more prominent by removing the version without the reflog parameters. | ||||
* | reflog: integrate into the ref writing | Carlos Martín Nieto | 2013-11-23 | 1 | -32/+0 |
| | | | | | | | | | | | | Whenever a reference is created or updated, we need to write to the reflog regardless of whether the user gave us a message, so we shouldn't leave that to the ref frontend, but integrate it into the backend. This also eliminates the race between ref update and writing to the reflog, as we protect the reflog with the ref lock. As an additional benefit, this reflog append on the backend happens by appending to the file instead of parsing and rewriting it. | ||||
* | refs: adjust to the new reflog API | Carlos Martín Nieto | 2013-11-23 | 1 | -2/+2 |
| | |||||
* | refs: Introduce git_reference_symbolic_create_with_log() | nulltoken | 2013-11-23 | 1 | -0/+31 |
| | |||||
* | refs: Introduce git_reference_create_with_log() | nulltoken | 2013-11-23 | 1 | -0/+52 |