| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
| |
Omitted a couple of files what have had significant contributions from
others.
|
|
|
|
|
|
|
|
| |
I forgot I had <$$> hidden away in Utility.Applicative.
It allows doing the same kind of currying as does >=*>
and I found using it made the code more readable for me.
(*>=> was not used)
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of populating the second-level Bloom filter with every key
referenced in every Git reference, consider only those which differ
from what's referenced in the index.
Incidentaly, unlike with its old behavior, staged
modifications/deletion/... will now be detected by 'unused'.
Credits to joeyh for the algorithm. :-)
|
|
|
|
| |
files are unwanted. This avoids a repreated drop/get loop of a file that has a copy in an archive directory, and a copy not in an archive directory. (Indirect mode still has some buggy behavior in this area, since it does not keep track of associated files.) Closes: #712060
|
| |
|
|
|
|
|
|
| |
Suggestion by Daniel Trstenjak
These are not currently mixed in my code base, so no real change.
|
| |
|
| |
|
|
|
|
|
|
| |
Nothing at all on hackage is using <&&> or <||>.
(Also, <&&> should short-circuit on failure.)
|
|
|
|
|
| |
(||) used applicative style runs both conditions rather than short
circuiting. Add an orM that properly short-circuits.
|
|
|
|
| |
no behavior changes
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|