Re: [PATCH] [RFD] Add repoid identifier to commit

TG> So what alternatives do we have ?

How about doing nothing of this sort, introducing repo-id? I do not understand what problem repo-id is solving.

Earlier in your response to Sean <seanlkml@sympaticoca>, you gave a QA department example.

TG> You have to track down a problem in bugfix and the source of it. TG> It does not matter whether the maintainer of "bugfix" pulled it from TG> devel or from stable. It's his fault anyway. TG> TG> But we are not talking about faults and guiltiness. We want TG> to identify the location and the context _where_ and _why_ TG> this change was created.

Here is my understanding of the scenario you are describing. Are these correct?

 - There is a problem in the source.

 - You know what lines of which file is causing the problem.
   But you cannot tell how the file got into that state and why
   by just looking at the problem revision.

 - You have the complete history (commit chain) leading to the
   revision.

 - You want to get some context to help you understand why those
   offending lines are there.

Assuming I am with you so far, I would like to know what kind of information you are looking for ("some context to help you understand"). Is a specific commit object (rather, one pair of commits that is parent-child) that made those lines into the current shape enough?

My understanding of Sean's argument is that finding such a commit (or a commit-pair) is a good enough place to start understanding why that change was introduced and finding who to ask for help, and it does not matter in which repository the change was introduced. I tend to agree with him if that is what is being discussed.

If the owner has multiple repositories and he needs to know in which of his repositories the change was introduced, I assume he would xsbe able to run the same procedure the QA department run to find the problem commit on each of his repositories to find such a commit, and commits around it (its ancestors and descendants). So a maintainer having more than one repositories does not seem to be an issue, either.

So I am having a hard time understanding what problem repo-id solves.