Older version ansible-modules-extras / source_control / bzr.py and stacked=yes

Archives Ansible Project
1

In an older version of bzr module I was able to use stacked=yes like this:

`

  • name: bzr branch --stacked lp:bzr-email
    bzr: name=lp:bzrtools dest=~“{{ansible_user}}”/.bazaar/plugins/email stacked=yes
    `

I decided to play with the github repository for ansible so I

git clone git://github.com/ansible/ansible.git --recursive

And I was surprised that stacked=yes was no longer supported so I did a

git log bzr.py

And all that was reported is this

`
$ git log bzr.py
commit b1e789968bdb5cbad54e86c0d09ec42213eafd7a
Author: Michael DeHaan michael.dehaan@gmail.com

File extensions!

`

Same info via github web interface

https://github.com/ansible/ansible-modules-extras/commits/devel/source_control/bzr.py

I’m a git newbie and don’t really understand the submodule stuff, but I’m wondering why the stacked=yes was removed and thought it would be in the git logs.

Thanks.

2

Git allows you to chase history across renames/moves with --follow:

#>git log --follow bzr.py

b1e789968bdb5cbad54e86c0d09ec42213eafd7a File extensions!
50f105578a07361e60f95a63da6acb5660765871 Restructuring.
ab4977e90981b6369013900d2bf1ff6740f207df Rename core to extras, prior to pruning steps.
73123b69fa5c15babaf28b2e5980b946ead1ace5 Move modules into subdirectory.
349063743f3d73690bf23a515ada96b8a06a6789 Some more run_command updates.
ef789865bbc388d73f3075bde646d442779dcd59 Force command action to not be executed by the shell unless specifically enabled
fc33860e5de5cdae1e010456357c0456da01ae89 Force command action to not be executed by the shell unless specifically enabled
38edad70acafbc18a0088470babdf94eff55a567 Fixes #5023 Convert all modules to use new snippet import pattern
1a9a6da4f73a55786e81692a3ccc9f1ad1d618ed fix docstring indentation on scc modules
3f74c2d986183f334c6c99394557512b012a1269 add executable option to bzr module, refactor in doing so
3404a0fc16221faffb65a8024187cff0f5436a3d DOCS: standardize on EXAMPLES (a.k.a. Docs-JumboPatch JetLag Edition) Migrated all examples: in DOCUMENTATION=‘’’ string to standalone EXAM
9c59057c1fa59f51deabae0e9f9e56ef0a1206c7 Docs standardization
cd97a4cb1459141cb5d4a0f28463dd39650caa68 Allow modules to be categorized, and also sort them when generating the documentation.
78f82a089d485b0407fe00e7a76df0bfd2605160 Fix bzr module documentation, name is the primary attribute.
c2f4c09c21fa4dde3d3d70b4a09c8ae30ca21987 Name should be the primary attribute for the ‘parent’ in the bzr module.
8243f797cfbe450e39e323af1b8d6f4c1bf95830 Fix version_added attribute on the bzr module
0417dc84186c00b5c958f671c90a9f88af35032a Added Bazaar module, based on the Git module

I don’t see a ‘remove stacked’ commit message, but it might be in one of those

3

Thanks. That was helpful. With that command I found this:

http://stackoverflow.com/questions/1337320/how-to-grep-git-commit-diffs-or-contents-for-a-certain-word

And like you already mentioned I don’t see “stacked” anywhere in the commit messages or the contents. Just posting the link for future generations.

4

Very very old versions of ansible might have allowed you to make up command arguments, in which case it might not have done anything :slight_smile: