Dear diary, on Sun, Apr 02, 2006 at 06:17:29PM CEST, I got a letter where Josef Weidendorfer <Josef.Weidendorfer@xxxxxx> said that... > > I would write the config like this: > > > > [branch-upstream] > > master = linus > > ata-irq-pio = irq-pio > > ata-pata = pata-drivers > > That is not working, as said above. But with above syntax extension, > with s/=/for/ it would be fine. I'm sorry but I'm slow and I don't see it - why wouldn't this work? (Except that the key name is case insensitive, which isn't too big a deal IMHO.) I for one think that the 'for'-syntax is insane - it's unreadable (your primary query is by far most likely to be "what's the upstream when on branch X", not "what branches is this upstream for"), would convolute the configuration file syntax unnecessarily and would possibly also complicate the git-repo-config interface. Pavel's syntax is much nicer. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ Right now I am having amnesia and deja-vu at the same time. I think I have forgotten this before. - : 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