Re: [RFC/PATCH 3/3] push: add 'prune' option
- From
Felipe Contreras <felipe.contreras@gmail.com>
- Date
- Feb 22, 2012, 23:06 UTC
- Message-ID
- <CAMP44s0DnVfd_Ged5rnhM4BF1jEtm4jzyq9sJAoEtQ-0CM5_aA@mail.gmail.com>
- In-Reply-To
- <CAMP44s3+XCM1E_AtW1yGifmGoGSkFSpSTaFbbMffz+hmUzWahw@mail.gmail.com>
On Wed, Feb 22, 2012 at 10:43 PM, Felipe Contreras <felipe.contreras@gmail.com> wrote:
Show 6 quoted lines
> On Sat, Feb 18, 2012 at 12:34 AM, Junio C Hamano <gitster@pobox.com> wrote: >> Does it make sense to specify --prune when --mirror is in effect? If so, >> how would it behave differently from a vanilla --mirror? If not, should >> it be detected as an error? > > Probably doesn't make sense, should be an error.
Actually, after writing the patch for the documentation I realized this would be difficult to describe: you can use --all --prune, but not --mirror --prune, and the documentation currently has '[--all | --mirror | --tags]'. So I decided to make it orthogonal, you can use --prune with --all, --tags, *and* --mirror. Of course, using --prune --mirror is the same as --mirror.
Cheers.
-- Felipe Contreras