Isn't a shallow clone a good use case for this? You only need the latest commit
of each project you want to build and then it either works or it doesn't, and
the clone is then deleted.
So is 'git clone --depth depth' what you need?
Use depth := 1
Just a thought
Philip
- Original
On Thursday, August 30, 2012 2:21:15 AM UTC+2, Haasip Satang wrote:
Hi all,
in short the question of the lenghty explanation below will be: How can I
create a clone of a subtree that only contains the data needed for that
subtree in the .git folder.
In detail here is what I have tried
;-) That's what I did as you can see in my explanation above ;-) The
problem still seems to be that it only works locally on the same linux
machine. When I try to clone from any remote machine (not matter which OS)
I end up getting the huge .git folder.
So the question actually is why does
Thanks Thomas,
I was looking into these Jenkins options as well, but as you said yourself,
it would be kind of a short-term hack and definitely would have big
impact on our feedback loop as we have a whole bunch of projects and
branches and of course would like to get timely feedback. (which
On Thursday, 30 August 2012 11:34:52 UTC+1, Haasip Satang wrote:
So the question actually is why does
git clone --depth 1 --no-hardlinks *file:///*home/me/gitTests/subtreeRepo
-b subtrees/xyz *xyz *
give me a small clone (*but only locally), *while cloning from remote I
get a big one.
On Thursday, August 30, 2012 1:04:56 PM UTC+2, Haasip Satang wrote:
Thanks Thomas,
I was looking into these Jenkins options as well, but as you said
yourself, it would be kind of a short-term hack and definitely would have
big impact on our feedback loop as we have a whole bunch of
On Aug 30, 11:34 am, Haasip Satang haasip.sat...@googlemail.com
wrote:
;-) That's what I did as you can see in my explanation above ;-) The
problem still seems to be that it only works locally on the same linux
machine. When I try to clone from any remote machine (not matter which OS)
I end
Yep, was having a similar setup with CruiseControl before we moved to
Jenkins. Really would love to avoid that. So while I like your ideas for
how to work aorund the problem and get the Jenkins stuff to work I would
still love to know why git is behaving this way (being a geek I can't sleep
at
I was expecting 'git log --after' to show me commits after a given date
time. What it does is includes the commit at the time stamp provided, why
is that? Is this a bug?
example - I've kept track of the date of my last commit by doing the
following:
git show -s --format=%ci a commit hash
I found something that might be interesting. To me the problem seems to be
the way the pack files are constructed.
I checked what happened with git log and what I get is the following:
/lhome/gitadmin/repo/main git log
commit 214baf2cea19d66e3a1817e8e6aa4883294be05f
Merge: ac974b0 8ad7c91
On Aug 30, 3:57 pm, Haasip Satang haasip.sat...@googlemail.com
wrote:
I found something that might be interesting. To me the problem seems to be
the way the pack files are constructed.
I checked what happened with git log and what I get is the following:
/lhome/gitadmin/repo/main git log
By the way... using file:// also works from remote, not only local. So
currently that's the solution for me (at least to get the builds up and
running on small repo clones).
I will do some more testing and reading with the other protocols and then
maybe file a bug report or at least ask in
Has anyone had any success with 'git svn clone' on Windows? I'm new to
git. We've been using subversion and I've been elected to migrate our
existing projects to git. I'm using version 1.7.11-preview20120710 and I'm
following the instructions from *
13 matches
Mail list logo
