The 67 Gb I mentioned earlier was wrong, I misread as I said in the next
post.
You downloaded 205.68 Mb but, because git re-use the same objects, once the
file structure is done, the space taken on the disk at the end is 2,61 Gb.
Well, anyway, the 205.68 Mb are normaly downloaded quickly at me, but not
from the apache servers, I'm in France and if I do a ping on
git-wip-us.apache.org[1] compared to google.com[2], as you can see there's a
hudge difference, so, instead of having few minutes of download, I've got
more than 2h30 (I wonder if it happens for everyone in europe).
Longer term, maybe each of us could create our own branches under the
whiteboard repo. Would that make sense?
Well, dispite the fact that it would accelerate the checkout, it's not the
normal usage, imagine, if a committer does more branches for its project(s),
that's going to become a lot of branches and those branches will have to be
named <CommitterName-Project-BrancheName> or something like that to be
easily identified.
-Fred
[1]
U:\sources\asf\flex\temp\flex-whiteboard>ping git-wip-us.apache.org
Envoi d'une requête 'ping' sur git-wip-us.apache.org [140.211.11.121] avec
32 octets de données :
Réponse de 140.211.11.121 : octets=32 temps=186 ms TTL=44
Réponse de 140.211.11.121 : octets=32 temps=185 ms TTL=43
Réponse de 140.211.11.121 : octets=32 temps=184 ms TTL=43
Réponse de 140.211.11.121 : octets=32 temps=190 ms TTL=43
Statistiques Ping pour 140.211.11.121:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 184ms, Maximum = 190ms, Moyenne = 186ms
[2]
U:\sources\asf\flex\temp\flex-whiteboard>ping google.com
Envoi d'une requête 'ping' sur google.com [2a00:1450:400c:c03::8a] avec 32
octets de données :
Réponse de 2a00:1450:400c:c03::8a : temps=32 ms
Réponse de 2a00:1450:400c:c03::8a : temps=30 ms
Réponse de 2a00:1450:400c:c03::8a : temps=35 ms
Réponse de 2a00:1450:400c:c03::8a : temps=35 ms
Statistiques Ping pour 2a00:1450:400c:c03::8a:
Paquets : envoyés = 4, reçus = 4, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 30ms, Maximum = 35ms, Moyenne = 33ms
-----Message d'origine-----
From: Om
Sent: Sunday, March 17, 2013 7:36 PM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
But it does not download the 67 Gb worth of data as you mentioned earlier.
The git repo objects is around 240MB. I suggest you do it as a one time
thing and after that use only your directory from the whiteboard.
Longer term, maybe each of us could create our own branches under the
whiteboard repo. Would that make sense?
Thanks,
Om
On Sun, Mar 17, 2013 at 11:22 AM, Frédéric THOMAS
<webdoubl...@hotmail.com>wrote:
The git remote fetch operation you do will get the entire repo, you then
apply a filter using the .git/info/sparse-checkout and you'll see only
your directory but first you fetched the entire repo, with your bandwith
that's ok, not with mine, while you are at 624 KiB/s I'm at 20 KiB/s
-Fred
-----Message d'origine----- From: Om
Sent: Sunday, March 17, 2013 6:55 PM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
In git bash:
omuppira@OMUPPIRA /c/p/flex_os/workspace/**flexroot/git/test
*$ git init*
Initialized empty Git repository in
c:/p/flex_os/workspace/**flexroot/git/test/.git/
omuppira@OMUPPIRA /c/p/flex_os/workspace/**flexroot/git/test (master)
*$ git remote add -f origin
https://git-wip-us.apache.org/**repos/asf/flex-whiteboard.git*<https://git-wip-us.apache.org/repos/asf/flex-whiteboard.git*>
Updating origin
remote: Counting objects: 67595, done.
remote: Compressing objects: 100% (41561/41561), done.
remote: Total 67595 (delta 23131), reused 67595 (delta 23131)
Receiving objects: 100% (67595/67595), 205.68 MiB | 624 KiB/s, done.
Resolving deltas: 100% (23131/23131), done.
From
https://git-wip-us.apache.org/**repos/asf/flex-whiteboard<https://git-wip-us.apache.org/repos/asf/flex-whiteboard>
* [new branch] master -> origin/master
omuppira@OMUPPIRA /c/p/flex_os/workspace/**flexroot/git/test (master)
*$ git config core.sparsecheckout true*
omuppira@OMUPPIRA /c/p/flex_os/workspace/**flexroot/git/test (master)
*$ echo bigosmallm/ >> .git/info/sparse-checkout*
omuppira@OMUPPIRA /c/p/flex_os/workspace/**flexroot/git/test (master)
*$ git pull origin master*
From
https://git-wip-us.apache.org/**repos/asf/flex-whiteboard<https://git-wip-us.apache.org/repos/asf/flex-whiteboard>
* branch master -> FETCH_HEAD
In the directory, you should see only .git/ and bigosmallm/ directories.
Hope this helps.
Unfortunately, TortoiseGit does not seem to support this feature. But
once
I set it up this way using Git Bash, I can continue to use TortoiseGit as
usual.
Thanks,
Om
On Sun, Mar 17, 2013 at 10:20 AM, Frédéric THOMAS
<webdoubl...@hotmail.com>**wrote:
It does seems to work for me, can you please give me the commands you
used.
-Fred
-----Message d'origine----- From: Om
Sent: Sunday, March 17, 2013 6:04 PM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
On Sun, Mar 17, 2013 at 9:33 AM, Frédéric THOMAS <webdoubl...@hotmail.com
>
**wrote:
Well, from what I'm reading about spare checkouts, I need to clone the
entire repo first, and only after, I can indicate that only this/those
tree(s) interest me, but I can't do it before it is already cloned.
Do you know something else about spares I didn't get ?
I tried this:
http://jasonkarns.com/blog/****subdirectory-checkouts-with-**<http://jasonkarns.com/blog/**subdirectory-checkouts-with-**>
git-sparse-checkout/<http://**jasonkarns.com/blog/**
subdirectory-checkouts-with-**git-sparse-checkout/<http://jasonkarns.com/blog/subdirectory-checkouts-with-git-sparse-checkout/>
>
It works out fine. I was able to get only my whiteboard (which has just
a
couple of files) It took only a few minutes for the checkout process.
Thanks,
Om
-Fred
-----Message d'origine----- From: Frédéric THOMAS
Sent: Sunday, March 17, 2013 5:21 PM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
Hi Om,
Good morning so :)
Well, not yet, actually, I was look for a such feature, I'm trying it
right
now.
Thanks for that tip,
-Fred
-----Message d'origine----- From: Om
Sent: Sunday, March 17, 2013 5:01 PM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
On Mar 17, 2013 8:43 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com>
wrote:
@Om,
At the end, the flex-withboard repo is 2,61 Gb on disk, it took more
than
2:30 to download, I really don't think that's something acceptable,
would
it be possible to split the repos, one by committer ?
Can you check that with David ?
-Fred
I am just woke up and am catching up on all the emails overnight. But
have
you tried the sparse checkout option in git?
Thanks,
Om
-----Message d'origine----- From: Michael Schmalle
Sent: Sunday, March 17, 2013 3:43 PM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
Yes, this looks correct, at least thats what my history says.
Mike
Quoting Frédéric THOMAS <webdoubl...@hotmail.com>:
@Mike, the falcon repo has history back to 2012-08-16, is that
correct
for you ?
-Fred
-----Message d'origine----- From: Frédéric THOMAS
Sent: Sunday, March 17, 2013 3:20 PM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
Yeah, I remember that, I remember as well I gave you a trick to run
Mustella
with a low priority, did you try it ?
Btw, I was looking closer at the wiki to build falcon and the sdk
dependencies you talk about, what they are ? that's not clear on the
wiki.
-Fred
-----Message d'origine----- From: Michael Schmalle
Sent: Sunday, March 17, 2013 3:14 PM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
I already did months ago, it almost crashed my computer.
Needless to say that is the last time I ran mustella.
Mike
Quoting Frédéric THOMAS <webdoubl...@hotmail.com>:
hehe, if you think downloading thirdparty/building the sdk is a pain,
don't even try to play with mustella tests ;-)
-Fred
-----Message d'origine----- From: Michael Schmalle
Sent: Sunday, March 17, 2013 3:05 PM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
Yeah, I already have it checked out and am in the process of building
it, my god this is a ridiculous process. I have never seen anything
harder to get going then the Flex SDK.
I'm still downloading the Adobe SDK for the freaking build!
I just asked about the branch type, remote or local. I'm just going
with remote.
I already built falcon half way and my other projects work fine
(built
the parsers, tokenizers). It failed when it wanted to COPY some of
the
sdk.
Whatever, this is exactly why I will never work on this sdk. Its a
huge amount of baggage left over from a huge corporation.
Mike
Quoting Frédéric THOMAS <webdoubl...@hotmail.com>:
I just looked at the wiki to figure out how to build falcon, I'll
need to install eclipse :P so, I'll do that tomorrow, today, I
guess
I
won't have time, once built, I'll do the .gitignore.
The wiki is still empty about git, but look at what Justin wrote [1]
(that's command line), if you're on windows, you can use
tortoiseGit
or
my prefered one smartGit and you'll just have to clone the flex-sdk
and
switch branch.
-Fred
[1]
http://markmail.org/message/******a6pa7bage42cceoy<http://markmail.org/message/****a6pa7bage42cceoy>
<http://**markmail.org/message/****a6pa7bage42cceoy<http://markmail.org/message/**a6pa7bage42cceoy>
>
<http://**markmail.org/**message/**a6pa7bage42cceoy<http://markmail.org/message/**a6pa7bage42cceoy>
<htt**p://markmail.org/message/**a6pa7bage42cceoy<http://markmail.org/message/a6pa7bage42cceoy>
>
>
[2]
https://code.google.com/p/******tortoisegit/wiki/Download<https://code.google.com/p/****tortoisegit/wiki/Download>
<http**s://code.google.com/p/****tortoisegit/wiki/Download<https://code.google.com/p/**tortoisegit/wiki/Download>
>
<http**s://code.google.com/p/****tortoisegit/wiki/Download<http://code.google.com/p/**tortoisegit/wiki/Download>
<htt**ps://code.google.com/p/**tortoisegit/wiki/Download<https://code.google.com/p/tortoisegit/wiki/Download>
>
>
[3]
http://www.syntevo.com/******smartgithg/download.html<http://www.syntevo.com/****smartgithg/download.html>
<http:**//www.syntevo.com/****smartgithg/download.html<http://www.syntevo.com/**smartgithg/download.html>
>
<http:**//www.syntevo.com/**smartgithg/**download.html<http://www.syntevo.com/smartgithg/**download.html>
<htt**p://www.syntevo.com/**smartgithg/download.html<http://www.syntevo.com/smartgithg/download.html>
>
>
-----Message d'origine----- From: Michael Schmalle
Sent: Sunday, March 17, 2013 2:40 PM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
Well, since Erik hasn't done it, I say if your on a roll, just do
it.
I don't like looking at a huge list of files that need to be
ignored.
:)
BTW;
Is there a thread that says how to properly check out the develop
branch of the sdk from Git GUI? I don't make a local copy right,
checkout as tracking branch correct?
I seriously hate this sdk. Way to big..., you wanna talk about
whiteboards, I'll talk about the sdk.
Mike
Quoting Frédéric THOMAS <webdoubl...@hotmail.com>:
Actually, I didn't plan to do that but if you or Erik doesn't
dare/want to do it, just tell me, I'll do it.
-Fred
-----Message d'origine----- From: Michael Schmalle
Sent: Sunday, March 17, 2013 2:28 PM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
Are you planning on getting the .gitignore in the falcon
directories
or is Erik doing this? I haven't been able to keep up.
Mike
Quoting Frédéric THOMAS <webdoubl...@hotmail.com>:
Hi,
I just committed the .gitignore into the flex-sdk repo, I'm
checking
how are flex-utilities and flex-whiteboard (at least mine) today,
while
I'll probably put the same .gitignore in the flex-utilities repo, I
advice
you guys to do the same with your personal repo.
Thinking about the asjs project, you can as well do the same, you'll
have to add some more exclusions.
@Justin, I really don't know what to write on the wiki about that,
it's like if we wanted to write something about svnignore, there
is
not
so much to say, once it is in the repo, it does what is has to do,
that's it.
If you think about something in particular I should write about
it, tell me pls because I'm like in front of a white page at the
moment.
Thanks,
-Fred
-----Message d'origine----- From: Justin Mclean
Sent: Sunday, March 17, 2013 1:28 AM
To: dev@flex.apache.org
Subject: Re: Committers - preparing for Git
Hi,
Btw, to all of you, I'm thinking about committing this file to
svn, like that when we'll clone the git repo, we'll already
have
it,
avoiding bad commits, what do you think ?
Add it to the "official" wiki page on git usage for Apache Flex -
which still needs some work.
Justin
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
--
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com
