hould never
get hit in the wild. Thanks for the patch!
Cheers,
Josh
On Fri, May 12, 2017 at 4:34 PM, Jeff King wrote:
> On Fri, May 12, 2017 at 10:19:59AM -0400, Josh Hagins wrote:
>
>> Since upgrading to Git 2.13.0 I'm seeing this error message whenever
>> `git config --loca
, argv=0x7fff5fbfe180)
at git.c:572
#10 0x00011883 in run_argv (argcp=0x7fff5fbfe12c,
argv=0x7fff5fbfe120) at git.c:624
#11 0x00010a4f in cmd_main (argc=4, argv=0x7fff5fbfe180) at git.c:701
#12 0x0001000c3772 in main (argc=5, argv=0x7fff5fbfe178) at common-main.c:43
Cheers,
Josh
On
rized release notes
published by GitHub specifically mentioned that instances of this
error message should be reported, so here you go!
Please let me know if I can provide any more information that would be helpful.
Cheers!
--
Josh Hagins
If neither git-submodule nor git-subtree is palatable to you, here are
a couple of alternatives you might try:
* https://github.com/ingydotnet/git-subrepo
* https://github.com/tdd/git-stree
On Tue, Jun 23, 2015 at 1:36 PM Stefan Beller wrote:
>
> On Tue, Jun 23, 2015 at 1:52 AM, Jean Audiber
I'm having a hard time understanding why ``git stash save" chokes on a
submodule removal when an empty directory is present at the removed
submodule's path. If the submodule is staged for deletion, why not
just leave the empty directory alone?
The following Gist illustrates the situation I am enco
5 matches
Mail list logo