From: Junio C Hamano <gitster@pobox•com>
To: Martin Langhoff <martin.langhoff@gmail•com>
Cc: Git Mailing List <git@vger•kernel.org>
Subject: Re: gc/repack has no option to lose grafted parents
Date: Thu, 06 Mar 2014 15:26:06 -0800 [thread overview]
Message-ID: <xmqqwqg6vrht.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CACPiFCLqa=ZQM6Azh2G5hwBCMx96Cxa5BMN=-2aCy5x=YhBpGg@mail.gmail.com> (Martin Langhoff's message of "Thu, 6 Mar 2014 18:07:06 -0500")
Martin Langhoff <martin.langhoff@gmail•com> writes:
> Back in http://git.661346.n2.nabble.com/PATCH-0-2-Make-git-gc-more-robust-with-regard-to-grafts-td3310281.html
> we got gc/repack to be safer for users who might be shooting
> themselves in the foot.
>
> Would a patch be welcome to add --discard-grafted-objects ? or
> --keep-real-parents=idontthinkso ?
>
> cheers,
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.
next prev parent reply other threads:[~2014-03-06 23:26 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 [this message]
2014-03-06 23:36 ` Martin Langhoff
2014-03-07 0:47 ` Duy Nguyen
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=xmqqwqg6vrht.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=martin.langhoff@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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