On 05/07/12 10:43, Lionel Elie Mamane wrote:
> On Wed, Jul 04, 2012 at 10:03:25PM -0300, Olivier Hallot wrote:
>
>> About ccache, I have this
>
>> tdf@olivier-Vostro-3500:~/git/core$ ccache -s
>> cache directory /home/tdf/.ccache
>> cache hit (direct) 38119
>>
On Wed, Jul 04, 2012 at 10:03:25PM -0300, Olivier Hallot wrote:
> About ccache, I have this
> tdf@olivier-Vostro-3500:~/git/core$ ccache -s
> cache directory /home/tdf/.ccache
> cache hit (direct) 38119
> cache hit (preprocessed)2777
> cache miss
On 2012-07-05 03:03, Olivier Hallot wrote:
Given I don't have a second drive, what figures should I improve here?
(Notebook with i5 and 6 GB RAM)
By yourself an SSD drive - laptop hard drives are generally very slow
beasts, typical 5400rpm drives.
Seriously, it will completely transform your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks gentlemen for the advise. Indeed must be the rebasing that
affects files.
About ccache, I have this
tdf@olivier-Vostro-3500:~/git/core$ ccache -s
cache directory /home/tdf/.ccache
cache hit (direct) 38119
ca
On 04.07.2012 13:20, Olivier Hallot wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
My (linux) build actually works but I face a stressing situation
Each time I do a git pull -r and then make, then tail_build seems to
build from scratch and takes hours to finish, making my work a PITA.
Hi,
On Wednesday, 2012-07-04 13:10:10 +0100, Michael Meeks wrote:
> git format-patch -1
> (cd ../push_tree ; git am) < 0001-foo-baa.patch
Just as a side note, this can be done in one command without leaving
intermediate files around:
git format-patch --stdout -1 | (cd ../push_tree ;
On Wed, 2012-07-04 at 08:20 -0300, Olivier Hallot wrote:
> Each time I do a git pull -r and then make, then tail_build seems to
> build from scratch and takes hours to finish, making my work a PITA.
Noel points out that my re-basing work has quite some ripple-through; I
try to chunk my wo
I think this is mostly because Michael Meeks is working his way through
relicensing the code, which means he is touching stuff near the bottom
of the dependency graph, which means everything gets rebuilt.
I've gotten into the habit of doing a pull and then a rebuild at the
end of my working
