[m-dev.] libatomic_ops submodule
paul at bone.id.au
Tue Oct 6 13:20:33 AEDT 2015
On Mon, Oct 05, 2015 at 07:47:48PM +1100, Zoltan Somogyi wrote:
> I have a couple of problems with the new libatomic_ops submodule.
> The first problem is that I keep getting this as part of my diffs:
> diff --git a/libatomic_ops b/libatomic_ops
> --- a/libatomic_ops
> +++ b/libatomic_ops
> @@ -1 +1 @@
> -Subproject commit 137001b1d9bddc0034de887c8e6ebc32893b1821
> +Subproject commit 137001b1d9bddc0034de887c8e6ebc32893b1821-dirty
> Does anyone know what causes this, and how to stop it, other than
> deleting the directory and fetching it again?
Because some generated files are kept in the libatomic_ops directory to
avoid a dependency on libtool, when they are regenerated for whatever reason
git recognises that you have uncommited changes there.
If you "deinitialise" your git submodules
$ git submodule deinit -f .
WARNING: you will loose unsaved changes in the submodules.
And re-initialise them:
Git keeps a cache of the remote repository. However it check with the
remote to see if there a new changes, but won't need to download the whole
thing again. If you don't want it to use any network access you can edit
prepare.sh and remove the --remote option from "git update".
I realize this isn't ideal, it still adds extra steps to our workflows. An
alternative might be allowing libtool as a dependency.
> The second is that I often change to the library directory by doing
> "cd ../libTAB", where TAB is my filename completion character.
> That used to work, but now libatomic_ops is also a valid completion
> of just "lib". Can we give this directory some name that doesn't
> get in the way like this?
I'm happy to hear suggestions for a new name.
More information about the developers