On Tue, Aug 19, 2014 at 7:54 PM, Junio C Hamano <gits...@pobox.com> wrote: > Sorry, but I cannot answer, as the only thing that I recall when > I hear "branch object" was that I heard the phrase used but > without much substance.
Just to avoid unnecessary misunderstanding, by the above, especially the "without much substance" part, I do not mean that those without code have no say in the way the project improves its product. It is true that this project does not operate in such a way that visionaries throw ideas for coding minions to implement. A person with an itch and idea on how to scratch that itch is expected to lead the design and code, possibly with help from others. But in order to ask others evaluate and join force to help with the design and make it real with code, you need to present your idea to sufficient level of detail to be actionable. By "actionable", consider the level of detail in which the proposed log message (not code or documentation update) of PATCH 15/18. Even though the message alone does not give any working code, or it does not even spell out the byte-level detail of how the protocol messages look like, people should be able to read enough details such as what kind of information a push certificate is to contain, when a certificate is created, how it is transferred, when and by whom it is received, how it will be used by the receiver, how a server operator can tweak his or her system to make use of the information, and how the newly added system component would fit into the existing system. In other words, the description should be sufficient to assess both how useful the end result would be, how much new work needs to be done to get there, and how well the resulting system as a whole would fit together well. I went back to the old thread to re-read the mention of "branch object", but I did not get an impression that the idea was presented to the actionable level of detail; at least not yet. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html