{"thread":{"id":"7784","subject":"Remote \"push\" syntax","startedAt":"2007-04-22T20:49:58Z","lastAt":"2007-04-22T20:49:58Z","messageCount":1,"participants":["Daniel Barkalow"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"40151","messageId":"Pine.LNX.4.64.0704221611040.27922@iabervon.org","threadId":"7784","inReplyTo":null,"subject":"Remote \"push\" syntax","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2007-04-22T20:49:58Z","receivedAt":"2007-04-22T20:49:58Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"I'm splitting the code for reading configuration of remotes out of \nbuiltin-push, for eventual use by builtin versions of additional commands, \nas well as to make git-push hopefully a bit nicer to use, so I'm wodnering \nabout details of the behavior I should match.\n\nIs it actually valid to have wildcards in the \"push\" configuration for a \nremote? git-push seems to skip them when looking at configuration files, \nand the documentation only talks about them being valid on the command \nline. Is there some reason to filter them out of the configurations, \nrather than just treating them as (unlikely) literals?\n\ngit-push currently always defaults to \"origin\", even if there is a \ndifferent remote configured for the current branch. It seems to me like \nusing the branch's remote would be better if there is one.\n\nDo we care about the order of precedence of ways of configurating remotes? \nThe current order is remotes > config > branches; it would be convenient \nto use config > remotes > branches, particularly because I'd like to read \nthe config file first to find out the branch configuration.\n\n\t-Daniel\n*This .sig left intentionally blank*\n"}]}