[lmi-commits] [lmi] master 5724e39 5/5: Suggest a workaround for a puzzling git error

[Greg Chicares]

branch: master
commit 5724e39170b056170e556a26cdaa0b089d137674
Author: Gregory W. Chicares <gchicares@sbcglobal.net>
Commit: Gregory W. Chicares <gchicares@sbcglobal.net>

    Suggest a workaround for a puzzling git error
    
    The proprietary product repository in an up-to-date chroot reported:
      $cd /opt/lmi/proprietary
      $git rev-parse --short HEAD
      e5094a5a
    whereas b1243539 was the HEAD of the same repository in an out-of-date
    chroot. A catchup bundle was created ["/path/to" replaces the original
    pathspec, which was too long to fit on a single line]:
      $git bundle create /path/to/catchup.bundle master b1243539
    and moved to the out-of-date chroot, where it looked okay:
      $git bundle verify /path/to/catchup.bundle
      The bundle contains this ref:
      e5094a5a820181422d52243cf8a6d40dc799d142 refs/heads/master
      The bundle records a complete history.
      /path/to/catchup.bundle is okay
    but this customary command failed:
      $git pull /path/to/catchup.bundle
      fatal: Couldn't find remote ref HEAD
    whereas this succeeded:
      $git pull /path/to/catchup.bundle master
---
 gwc/develop2.txt | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/gwc/develop2.txt b/gwc/develop2.txt
index aed1c12..a72f83e 100644
--- a/gwc/develop2.txt
+++ b/gwc/develop2.txt
@@ -46,6 +46,12 @@ cd /opt/lmi/proprietary
 git bundle verify /path/where/you/saved/TheirBundleName
 git pull /path/where/you/saved/TheirBundleName
 
+  # [if git-pull fails with
+  #   fatal: Couldn't find remote ref HEAD
+  # try adding 'master at the end...
+
+git pull /path/where/you/saved/TheirBundleName master
+
   # ...then synchronize your "blessed" repository with your correspondent's
 
 git push