On 2008-02-26, Matthieu Moy <Matthieu.Moy@xxxxxxx> wrote: >> Right. That's why this would be a per-repo setting. It wouldn't be >> pulled or cloned, just looked up when needed. > > I think it should. Not versionned, but initialized by "clone" based on > the cloned repo. That would work. > The advantage of a clone-time initialization compared to a submit-time > look up is that the local user can very easily change the value > manually after a clone. You could always make it work like this: * If an address is given on the command line, use that. * Otherwise, if an address is given in config, use that. * Otherwise, look up the address at the remote repo; if successful, use that. * Otherwise, prompt the user. The advantage of this is that if the submission address changes (but the remote repo URL hasn't), then patches can automatically go to the right place. Of course the disadvantage is that the config is not initialized for offline mail queuing at clone time. I have generally found that not being able to queue patches offline isn't a big deal to me. Of course, someone could effectively do that also be using format-patch as it is normally used now. -- John - To unsubscribe from this list: 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
