Here is my previous review comments in a squashable patch form. The
result seems to pass all 27 combinations (fetch.prune, remote.*.prune
and command line all are tristate yes/no/unspecified).
Without the fix-up in *.c files, three combinations seem to fail.
Documentation/config.txt | 3 +-
$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
Michael Schubert msc...@elegosoft.com writes:
$gmane/201715 brought up the idea to fetch --prune by default.
When you can summarize it in a few lines, e.g.
Without git fetch --prune, remote-tracking branches for a branch
the other side already has removed will stay forever. Some
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
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
5 matches
Mail list logo
