Hi, > Can the empty commits be made to eg the master git branch? Well, you can _link_ to/from the master branch through additional parents. But we rely on the parent relationship between individual messages. Adding all messages to a single branch would effectivly make the issues indistinguishable from another and "break stuff".
> The man page seems to say so, but other documentation talks about > refs/dit/<issue-hash>/head branches. Then the man-page is not clear enough. We use refs under `refs/dit/<issue>/...` for keeping issue messages/commits addressable. The "head" ref is a special ref which always exists for an issue. The semantics are _kinda_ that of a brnach, but not exactly. It's more a tool for tracking the current state of the issue. > I em envisioning this workflow: > > * There's a bug in master, so I use git-dit to add an empty commit to > master describing the bug. As described above, the new issue/bug-report is not added to master, but to a commit which is referred to by a new head reference. > * I push my changes to origin. I may not be able to normally push > changes to origin/master, but since no files in the tree are > changed, a hook allows the push. On our somewhat opaque list of features to be implemented are helper scripts which could be used in a hook to allow pushing new issues and messages but disallow anything else (without authorization). > * A new version is released, unfortunately it does not fix my bug. > It gets shipped by some distributions. > * The maintainer creates a bugfix branch and fixes my bug in there, > or so they think. They use git-dit to mark it as probably fixed. > * I can pull that branch, test that it fixes the bug, use git-dit to > close the bug, and push to origin/bugfix. > * The maintainer merges bugfix into master, and so git-dit can tell > us that the bug is fixed there. > * git-dit can also tell is that the bug is still open in the > version that was released after I filed the bug report. That would be a possible and reasonable workflow. Once we support proper filtering of issues, that is. > BTW, your use of messages that correspond to emails reminds me of Lars > Wirzenius's http://distix.eu/ , which actually integrates with email > and stores the data in git as text files in a branch. I feel that > there might be an opportunity to combine the two. Thanks for the hint. We'll have a look. Mind adding it to the following list? https://dist-bugs.branchable.com/software/ Regards, Jule _______________________________________________ dist-bugs mailing list [email protected] https://kitenet.net/cgi-bin/mailman/listinfo/dist-bugs
