On Tue, Oct 4, 2011 at 9:00 AM, Jeff King <peff@xxxxxxxx> wrote: > On Mon, Oct 03, 2011 at 02:16:08PM +0200, Erik Faye-Lund wrote: > >> I recently needed to prune remote branches in a repo with a lot >> of remotes, and to my surprise "git remote prune" didn't support >> the --all option. So I added it. Perhaps this is useful for other >> people as well? > > You could do: > > git remote update --prune > > But I thought we were trying to get away from remote doing fetch-like > things in the long term. Isn't the "right" way to do this these days: > > git fetch --all --prune > > ? > > -Peff > I wasn't aware that fetch could prune, but yeah, that seems much better to me. Perhaps a mention of this in the "git remote prune" documentation could steer other users in the right direction? -- 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