Hi, I'm one of the authors of the tool.
> I see, so you are basically creating second DAG inside Git > repository... Have you tested any GUI git clients how they look at > it? Well, I regularly use `git log --oneline --graph --decorate --all` for viewing the history. `git log` does show the refs and messages if the `--all` parameter is supplied, so I see issue messages. The most annoying thing imo are the long references which are printed due to the `--decorate` parameter. Maybe I'll use `--decorate=short` or something in the future. I presume graphical tools will most probably abbreviate long reference-names, or show only branches. But I don't have much experience using GUI tools for git. Matthias regularly uses `tig`, which is a curses tool. Maybe he'll share some of his experience. > What's your plan for attachments? We're not quite sure how to handle those, yet. Theoretically, we could add attachments as mime-data to the issue message, but that would be insane. In most cases, issues have an empty tree. So, we could add attachments as blobs in the tree (e.g. how regular files are stored). This is obviously not possible for patch-sets, but attachments are most often used in bug-reports, anyway. Also, a friend of mine pointed out that in "enterprise use-cases", the attachments of bug-reports may end up rather large (binary blobs, with debuggng symbols and core-dumps). Someone suggested using/supporting git-annex for such use-cases in order to keep the repo small. Regards, Jule _______________________________________________ dist-bugs mailing list [email protected] https://kitenet.net/cgi-bin/mailman/listinfo/dist-bugs
