git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duy Nguyen <pclouds@gmail.com>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: Stas Cherkassky <scherkas@gmail.com>,
	Andrew Ardill <andrew.ardill@gmail.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: collapsing old git history to reduce repo size, while preserving commit #s and tags
Date: Wed, 30 Oct 2013 23:06:08 +0700	[thread overview]
Message-ID: <CACsJy8BcJMTeyku-37v5pwVvYFixaP2sLMQ24WaerKf8C9-AAw@mail.gmail.com> (raw)
In-Reply-To: <52712BF2.2080409@gmail.com>

On Wed, Oct 30, 2013 at 10:55 PM, Jakub Narębski <jnareb@gmail.com> wrote:
> On 2013-10-30 08:52, Stas Cherkassky wrote:
>>
>>
>> Shallow clone (if that's what you meant) is not suitable because it
>> doesn't allow to push/pull to/from this shallow repository.
>
>
> Still?  I think there were some work on making shallow clone to
> allowing push/pull to/from it.

Yes, still :-) I've got a proof of concept, but it needs more work to
address the concern about its automatically turning a full repo into a
shallow one.
-- 
Duy

      reply	other threads:[~2013-10-30 16:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJSXqrr4nA6azBgaD7rBbYSLWonQkn7PvSsPTXjAPaxW6E+LiA@mail.gmail.com>
2013-10-29 22:42 ` collapsing old git history to reduce repo size, while preserving commit #s and tags Stas Cherkassky
2013-10-29 22:52   ` Andrew Ardill
     [not found]     ` <CAJSXqrr7rHxyXX=_+xgJ4FW2UHSts2jRt7zwrkkw1L3uKHnCtw@mail.gmail.com>
2013-10-30  7:52       ` Stas Cherkassky
2013-10-30 15:55         ` Jakub Narębski
2013-10-30 16:06           ` 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=CACsJy8BcJMTeyku-37v5pwVvYFixaP2sLMQ24WaerKf8C9-AAw@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=andrew.ardill@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=scherkas@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).