>> I wonder why you decided to use Git this way. > Mainly because we strongly beleive that issues belongs to code in some > way.
Could you give an example of what you mean here? [ If you could contrast it with what happens in BuGit, that'd be even better. ] > With git-dit, you get the functionality to incooperate issues > _into_ your source-code history. Hmm... I must have misunderstood something: AFAIK dit issues are "sets of Git refs" (under refs/dit/<issueid>), so I can see that you can hold them in the same repository as your code (just like you can with BuGit), but I don't see how you can have it in your code's *history*. Oh, wait, do you mean that when you commit a fix to your code, you would add a second parent to that commit which refers to the issue that's fixed? So instead of having a special marker (says "Fixes: issue#<foo>") in your commit message, you refer to the issue as a parent? Hmm... that sounds interesting. I wonder what that allows you to do that the "Fixes: issue#<foo>" doesn't, tho. I can see that it makes sure your issues-history is always preserved in the code-history, but I'm not sure if that's a feature. > For example bugs can be files on a certain commit I don't understand what you mean by that. > Also, but maybe only as side-note: We are CLI freaks and we think git > is great... why not re-using its functionality for our goals? If you take a quick look at BuGit (https://gitlab.com/monnier/bugit), you'll see that we strongly agree on that front. Its design is also somewhat close to that of git-dit (except I do use files in my commits, e.g. for attachments, and I keep a single ref per issue). [ The main problem of BuGit (other than lack of manpower) is that it needs to be rewritten from scratch since it's currently just an sh script. ] One more thing, in https://github.com/neithernut/git-dit/blob/master/doc/datamodel.md you say that message metadata is kept in the form of "git-tags". Do you mean the same tags as those managed by "git tag"? How does that work? Stefan _______________________________________________ dist-bugs mailing list [email protected] https://kitenet.net/cgi-bin/mailman/listinfo/dist-bugs
