Using git for patch management in Fedora
Alek Paunov
alex at declera.com
Tue Nov 19 18:22:47 UTC 2013
On 19.11.2013 19:32, Daniel P. Berrange wrote:
> On Tue, Nov 19, 2013 at 07:27:20PM +0200, Alek Paunov wrote:
>> What about intermediate step: optional "fNN-upstream" branch in
>> addition to fNN, containing relevant upstream revision as git
>> submodule (preferably referencing fedorahosted mirror, but initially
>> also allowing "external" clones)?
>
> I think it would be better to keep the upstream repo separate for
> sake of size. People who just want to checkout the latest RPM
> branches don't want to have to pull down 100's of MB, potentially
> GB, worth of GIT repo, when current Fedora GIT repos are a mere
> few MB. Only maintainers actively updating patches need that
> burden.
>
Git submodules are just references to external revision, not
materialized inclusion of the referenced repo, aren't they?
Someone should explicitly add --recursive or git submodule command to
pull them.
Kind Regards,
Alek
I just checked once again:
git clone https://github.com/JulesAU/node-msgpack
Working directory contains file .gitmodules with 3 lines:
[submodule "deps/msgpack-full"]
path = deps/msgpack-full
url = https://github.com/msgpack/msgpack.git
Site web interface shows:
https://github.com/JulesAU/node-msgpack/tree/master/deps
git submodule status:
-d642487f9916dfe571531d0c6d0727b3ee449d36 deps/msgpack-full
ls -al deps/msgpack-full:
total 8
drwxrwsr-x 2 alek src 4096 Nov 19 20:06 .
drwxrwsr-x 3 alek src 4096 Nov 19 20:06 ..
However if:
git clone --recursive https://github.com/JulesAU/node-msgpack
node-msgpack-with-deps
ls -al deps/msgpack-full:
total 72
drwxrwsr-x 15 alek src 4096 Nov 19 20:14 .
drwxrwsr-x 3 alek src 4096 Nov 19 20:13 ..
drwxrwsr-x 4 alek src 4096 Nov 19 20:14 cpp
drwxrwsr-x 2 alek src 4096 Nov 19 20:14 csharp
...
More information about the devel
mailing list