Hello, The git-remote documentation talks about a mysterious -n option for show and prune that comes from the old git-remote.perl script. This flag was used to prevent the script from calling ls-remote more than once, FWIU. Today, the builtin accept an (un)?related -n(--dry-run) flag that does nothing, actually. It seems broken. So, is it safe to drop it entirely or is it better to just remove it from the documentation for compatibility? In the second case, how long should we wait before using --dry-run for something different? I would like to make "git remote prune" more verbose and use --dry-run to really prevent it from deleting stale tracking branches. $ git remote prune origin -n Pruning origin From: git://.../myproject.git * [stale branch] bla * [stale branch] bli * [stale branch] blu What about something like that ? Olivier. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| David Miller | Re: [PATCH] Stop pmac_zilog from abusing 8250's device numbers. |
| Andrew Morton | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 010/196] Chinese: add translation of Codingstyle |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | Re: [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Felix von Leitner | socket api problem: can't bind an ipv6 socket to ::ffff:0.0.0.0 |
git: | |
