git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duy Nguyen <pclouds@gmail.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: gc/repack has no option to lose grafted parents
Date: Fri, 7 Mar 2014 07:47:29 +0700	[thread overview]
Message-ID: <CACsJy8BrnKPu=Uf5Qy1KoccorBJ43yo+R9P3PyVAeNU9FuCy6Q@mail.gmail.com> (raw)
In-Reply-To: <CACPiFCLgoGP59sW73YFCt8Wq4hpxZUb0PBF-DzHz0JdxrYo4rw@mail.gmail.com>

On Fri, Mar 7, 2014 at 6:36 AM, Martin Langhoff
<martin.langhoff@gmail.com> wrote:
> On Thu, Mar 6, 2014 at 6:26 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Given that we in general frown upon long-term use of grafts (or
>> "replace" for that matter), I am not sure if we want to go in that
>> direction.
>>
>> Just a knee-jerk reaction, though.
>
> Fair enough.
>
> If I state my actual goals -- discarding old, uninteresting history,
> in a "rolling" fashion? (periodically using a script that says "forget
> anything older than one month") -- is there a better way?

Convert it to a shallow repository? Either you clone it and do "fetch
--depth=XXX && prune", or you manipulate $GIT_DIR/shallow directly
then prune (no worse than editing grafts, I think).
-- 
Duy

      reply	other threads:[~2014-03-07  0:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 23:07 gc/repack has no option to lose grafted parents Martin Langhoff
2014-03-06 23:26 ` Junio C Hamano
2014-03-06 23:36   ` Martin Langhoff
2014-03-07  0:47     ` Duy Nguyen [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACsJy8BrnKPu=Uf5Qy1KoccorBJ43yo+R9P3PyVAeNU9FuCy6Q@mail.gmail.com' \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=martin.langhoff@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).