Vesko Karaganev

Agreed on all points expect the machine readability by default. I think useful output by default is better for new (all?) users. When machine readability is desired it could be...

> One issue I'd not considered much yet was what to do if a snapshot and a pack are ambiguous, if list were to accept both packs or snapshot. I...

After more than 2 months, I have some more thoughts :) **Unique snapshots:** I like the idea of outputting the simple, unqualified snapshots and I understand the role disambiguating between...

Given ``` m:a1 m:a2 n:a1 n:a3 ``` What would the list output be according to your suggestion? ``` a2 a3 m:a1 n:a1 ``` Wouldn't that be confusing if expecting to...

elfshaker find prints all snapshots without sorting and the output can be fed back into elfshaker. We do that in manyclangs-run to match commit SHA to snapshot. I prefer optimising...

I'd be happy if we could allow more characters in snapshot tags. I see the value in adding '.' in particular. I've concerns for allowing spaces through - handling spaces...

We use `EXTRA_ID_CHARS` for both packs and snapshots and packs have 1-1 correspondence with files on the filesystem (minus the file extension). If `.` is also desirable for pack names...

I agree it is better to keep the pack and snapshot naming rules the same. Allowing `.` in pack names just requires a bit more work, but is definitely doable....

There isn't one. The format is simple enough to be edited by hand. Or one could use the following to append a .pack: ```sh printf "%.40s\t%.40s\t%s" "$(sha1sum ./A.pack.idx)" "$(sha1sum ./A.pack)"...

Thanks for the suggestion! You can make an application run in floating mode by adding the process to the Exclusions list (found in Settings > Exclusions). For example, to run...