> I released today git-bug, a distributed bug tracker that embeds in git.
[ For reference, my take on this problem is embedded in the design of BuGit https://gitlab.com/monnier/bugit. ] > [1]. In short, bugs are stored as a series of edit operations stored in git > blobs and assembled in a linear chain of commits. This doesn't in itself ensure a lack of conflicts: you additionally need to ensure that those edit commands don't conflict between themselves, either by making them commute or by making them "arbitrarily conflict free" (in this latter case, you run the risk of having merges result in something which the user wouldn't consider as correct). E.g. for SET_TITLE, if two users use this command at the same time, the merge will likely just order them arbitrarily, so one of the two operations ends up ineffective (IIRC that's also what I do in BuGit in the case of changes to the title). Stefan _______________________________________________ dist-bugs mailing list [email protected] https://kitenet.net/cgi-bin/mailman/listinfo/dist-bugs
