From: Martin Atukunda <matlads@dsmagic.com>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Allow git-repack to optionally run git-prune-packed.
Date: Thu, 9 Mar 2006 13:24:19 +0300 [thread overview]
Message-ID: <20060309102419.GA9961@igloo.ds.co.ug> (raw)
In-Reply-To: <20060307212918.GA9474@steel.home>
Your suggestion has merit, though it's different from the behaviour I
desired. I _sometimes_ need the pruning, and it felt appropriate to make
it an option as opposed to default behaviour.
What do you think?
- Martin -
On Tue, Mar 07, 2006 at 10:29:18PM +0100, Alex Riesen wrote:
> Martin Atukunda, Tue, Mar 07, 2006 16:16:12 +0100:
> > +-p::
> > + Run `git-prune-packed` after packing, see
> > + gitlink:git-prune-packed[1]
> > +
>
> Maybe just make "-d" work? I.e. "git repack -a -d" repacks and prunes
> everything, and "git repack -d" prunes just what was packed
> incrementally.
> Something like this:
>
> diff --git a/git-repack.sh b/git-repack.sh
> index 3d6fec1..be6c7ab 100755
> --- a/git-repack.sh
> +++ b/git-repack.sh
> @@ -74,6 +74,8 @@ then
> esac
> done
> )
> + else
> + git-prune-packed
> fi
> fi
>
>
> -
> 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
--
Girl on cell: Can you hear me when I roll my eyes?
-- www.overheardinnewyourk.com
next prev parent reply other threads:[~2006-03-09 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 15:16 [PATCH] Allow git-repack to optionally run git-prune-packed Martin Atukunda
2006-03-07 21:29 ` Alex Riesen
2006-03-09 10:24 ` Martin Atukunda [this message]
2006-03-09 14:48 ` Alex Riesen
2006-03-09 18:50 ` Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060309102419.GA9961@igloo.ds.co.ug \
--to=matlads@dsmagic.com \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).