Changes between Version 20 and Version 21 of faq/gitification


Ignore:
Timestamp:
May 28, 2012, 2:37:24 PM (13 years ago)
Author:
Bart
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • faq/gitification

    v20 v21  
    252252}}}
    253253
    254 This approach won't work for git-subtree as remotes are not exported so a [http://git-scm.com/docs/git-clone git-clone] won't know the original fetch urls used for {{{git subtree add}}}. Fortunaltely, drupal.org uses well-defined fetch urls so we can reconstruct the information. But the process will be much more complicated and time-consuming with git-subtree than it is with git-submodule as we would either have to keep the module's history in a separate branch, incorporate the whole history by not using the --squash parameter, (temporarily) clone the module or use [http://git-scm.com/docs/git-ls-remote git-ls-remote].
     254This approach won't work for git-subtree as remotes are not exported so a [http://git-scm.com/docs/git-clone git-clone] won't know the original fetch urls used for [https://github.com/apenwarr/git-subtree/blob/master/git-subtree.txt git-subtree-add]. Fortunaltely, drupal.org uses well-defined fetch urls so we can reconstruct the information. But the process will be much more complicated and time-consuming with git-subtree than it is with git-submodule as we would either have to keep the module's history in a separate branch, incorporate the whole history by not using the --squash parameter, (temporarily) [http://git-scm.com/docs/git-clone git-clone] the module or use [http://git-scm.com/docs/git-ls-remote git-ls-remote].
    255255
    256256Keeping the whole history in a separate branch would work but this is a fragile approach because we'd lose the liberty to mess around with our repository which is one of the key advantages of the git-subtree approach compared to the git-submodule one. We do want to use the --squash parameter to keep the overall size of the git repo small and the git history uncluttered. So the only remaining way to go is to either clone the repository to determine the necessary info locally or use git-ls-remote to search on git.drupal.org.