On Mon, 2006-05-08 at 03:27 +0200, Johannes Schindelin wrote: > > Now, how can I get a description for the "netdev" branch by one > > git-repo-config command, without pipes? > > git-repo-config --get branchdata.description ' for netdev$' No, it doesn't remove "for netdev". What I really don't like is that git-repo-config treats it as "not my problem". git-repo-config places extremely tight limitations of the names of the sections and the keys. But sometimes a relationship between two loosely defined strings needs to be presented. It's a real need. And git-repo-config doesn't address this need. I believe git-repo-config should allow direct retrieval of data from any depth, and the syntax should be explicit rather than fuzzy. A dot is more explicit than "for", especially if the dot appears after a name that may not contain dots. Another question is how we want to group the data. Do we want to have all descriptions together or in separate sections? Whatever the answer, git-repo-config should provide means to extract all data in one command, without need for postprocessing. So I understand arguing where to place the branch name. But what I don't like is the desire to offload part of the processing on the callers. -- Regards, Pavel Roskin - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html