| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
| |
Simply HEAD is not displayed by gitk, which is rather a shame.
|
|
|
|
|
| |
When we unmerged some old A+B merged refs, make a note to merge them
again. This saves the user calling gitfetchinfo-merge again.
|
|
|
|
|
|
| |
* Turn on perl warnings
* Use strict
* When removing old merged refs, insist that we aren't handling A+A
|
|
|
|
|
|
|
|
|
|
|
|
| |
The sequence
gitfetchinfo-merge A B
gitfetchinfo A
gitfetchinfo-merge A B
might leave inappropriate A+B refs, because nothing would delete them.
So, have gitfetchinfo A unmerge any A+B or B+A refs. (This does mean
that the user of gitfetchinfo A is now promising that any remotes A+B
or B+A were made with gitfetchinfo-merge.)
|
|
|
|
|
|
| |
We want the commit timestamps to be predictable (ie, to depend on the
source info only), so that we don't show spurious disagreement between
two working trees. So, use the timestamp of the HEAD commit.
|
| |
|
| |
|
|
|
|
| |
Help with comparing different test case git working tree tarballs.
|
|
|