From: Basin Ilya <basinilya@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: test bare repository for unit tests
Date: Thu, 22 Feb 2018 10:47:55 +0300 [thread overview]
Message-ID: <2d901963-b66b-8f7a-a6ac-76a334aeb1da@gmail.com> (raw)
In-Reply-To: <878tbmeyz2.fsf@evledraar.gmail.com>
Hi.
git-fast-export would work too, but it creates an additional step. I don't commit to the model repo during tests, but I do commit when I want to modify the tests.
So far, I configured core.compression=0 and gc.auto=0, created the .gitattributes inside the bare repo dir containing one line: * binary
I also created two empty .gitignore files inside refs/ and objects/
I still haven't found a way to force prune without pack after each push.
On 22.02.2018 1:53, Ævar Arnfjörð Bjarmason wrote:
>
> On Wed, Feb 21 2018, Basin Ilya jotted:
>
>> Hi.
>> I want to the test-repo-git under https://github.com/apache/maven-wagon/tree/master/wagon-providers/wagon-scm/src/test/resources/
>> just like test-repo-cvs and test-repo-svn
>>
>> Which configuation options would suit that?
>> I think core.compression 0 for human readable diffs.
>> also, I need to force loose, gc after each push.
>
> It looks like you have unit tests that are going to do integration tests
> of some SVN/CVS repos as used by some other tool, and want to add git to
> that.
>
> Since you have git already, the most straightforward thing to do would
> be to ship the output of git-fast-export in the repo, and have the test
> setup code create a repo locally out of that, then test it.
>
> Or do you really need to commit the raw repo files as-is for some reason
> I've missed?
>
prev parent reply other threads:[~2018-02-22 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 8:33 test bare repository for unit tests Basin Ilya
2018-02-21 22:53 ` Ævar Arnfjörð Bjarmason
2018-02-22 7:47 ` Basin Ilya [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2d901963-b66b-8f7a-a6ac-76a334aeb1da@gmail.com \
--to=basinilya@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).