On Unix, subpackages are written like this:

-name github.com/foo/bar
 version: xxxxx
 subpackages:
 - baz
 - baz/qux

However, on Windows, the subpackages are written as:

-name github.com/foo/bar
 version: xxxxx
 subpackages:
 - github.com\foo\bar\baz
 - github.com\foo\bar\baz\qux

Notice how the full package path is used with backslashes, even though the repo name uses forward slashes.

If an update is performed on Windows on a lockfile created on a Unix machine, the subpackages are duplicated:

-name github.com/foo/bar
 version: xxxxx
 subpackages:
 - baz
 - baz/quz
 - github.com\foo\bar\baz
 - github.com\foo\bar\baz\qux

Again, notice how the original Unix subpackages are using forward slashes while the ones written on the Windows host are using backwards slashes.

I haven't noticed any issues with glide resulting from these differences (yet), but as I develop on both operating systems I would prefer the output to be the same from each.

This was experienced using glide master (as of 0f53710).