>That said, is there any plan to change how this functions in the future
>to solve these problems? I.e. have it not use so much diskspace and
>thus use less bandwith. Am I misunderstanding in assuming that after
>say 1000 commits go into the tree it could end up several megs or gigs
>bigger?
>
>If that is the case might it not be more prudent to sort this out now?
Only a new user would have to pull the whole history ... and for most
uses it is sufficient to just pull the current top of the tree. Linus'
own tree only has a history going back to 2.6.12.-rc2 (when he started
using git).
Someday there might be a server daemon that can batch up the changes for
a "pull" to conserve network bandwidth.
There is a mailing list "[email protected]" where these issues are
discussed. Archives are available at marc.theaimsgroup.com and gelato.
-Tony
Luck, Tony wrote:
<SNIP>
> Only a new user would have to pull the whole history ... and for most
> uses it is sufficient to just pull the current top of the tree. Linus'
> own tree only has a history going back to 2.6.12.-rc2 (when he started
> using git).
>
> Someday there might be a server daemon that can batch up the changes for
> a "pull" to conserve network bandwidth.
>
> There is a mailing list "[email protected]" where these issues are
> discussed. Archives are available at marc.theaimsgroup.com and gelato.
>
Thanks tony I wasn't aware of the list, I'll look there for git info
from now on.
Best Regards,
Stan
> -Tony
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>