On Mon, Nov 7, 2011 at 11:25 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Jeff King <peff@xxxxxxxx> writes: > >> That makes sense. But I think it fits in with git's current UI to do >> this via a combination of push options and refspecs. Even if we want to >> wrap it in some "git remote" command for convenience, I think what >> you're asking should be implemented as part of "git push". > > Yeah, I think it makes sense to give --prune to "push" just like "fetch" > already has. These two are the primary (and in the ideal world, only) > operations that talk to the outside world. "remote add -f" might have been > a tempting "convenience" feature, but I personally think it probably was a > mistake for the exact reason that letting anything but "push" and "fetch" > talk to the outside world just invites more confusion. There does not have > to be 47 different ways to do the same thing. What about 'git remote update'? -- Felipe Contreras -- 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