From: Jeff King <email@example.com> To: Michael Schubert <firstname.lastname@example.org> Cc: email@example.com Subject: Re: [RFC/PATCH] fetch: make --prune configurable Date: Mon, 8 Jul 2013 23:50:08 -0400 [thread overview] Message-ID: <20130709035008.GA27903@sigill.intra.peff.net> (raw) In-Reply-To: <firstname.lastname@example.org> On Mon, Jul 08, 2013 at 02:56:57PM +0200, Michael Schubert wrote: > $gmane/201715 brought up the idea to fetch --prune by default. > Since --prune is a "potentially destructive operation" (Git doesn't > keep reflogs for deleted references yet), we don't want to prune > without users consent. > > To accommodate users who want to either prune always or when fetching > from a particular remote, add two new configuration variables > "fetch.prune" and "remote.<name>.prune": > > - "fetch.prune" allows to enable prune for all fetch operations. > > - "remote.<name>.prune" allows to change the behaviour per remote. Thanks. As the person who brought up the destructive nature of --prune in the thread you mentioned, I have no problem at all with doing something like this, where the user gets to make the choice. And it is even a good building block if we later do have deleted-branch reflogs; we can just flip the default from "off" to "on". In the meantime, I don't know if it is worth mentioning in the documentation that the remote branches are hard to get back. On the one hand, it is the (or at least a) reason why the default is not "on". But it is also far from the only place refs get deleted, so I don't know if it is worth calling attention to it specifically. -Peff
prev parent reply other threads:[~2013-07-09 3:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-08 12:56 Michael Schubert 2013-07-08 18:36 ` Junio C Hamano 2013-07-12 22:38 ` Junio C Hamano 2013-07-08 19:01 ` John Keeping 2013-07-09 3:50 ` Jeff King [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20130709035008.GA27903@sigill.intra.peff.net \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [RFC/PATCH] fetch: make --prune configurable' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).