Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-2448

No prepare-commit-msg and commit-msg files on b2_1

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Minor
    • Lustre 2.1.4
    • Lustre 2.1.3
    • None
    • 3
    • 5786

    Description

      No prepare-commit-msg and commit-msg files on b2_1 and hoks links to both are broken. we see these files on b1_8, b2_2 and b2_3, but no them on b2_1.

      $ git checkout --track -b b2_1 origin/b2_1
      Branch b2_1 set up to track remote branch b2_1 from origin.
      Switched to a new branch 'b2_1'
      
      $ ls -l .git/hooks/prepare-commit-msg
      lrwxr-xr-x  1 ihara  staff  30 Dec  1 13:03 .git/hooks/prepare-commit-msg -> ../../build/prepare-commit-msg
      
      but, file is not accessible since 
      
      $ cat .git/hooks/prepare-commit-msg
      cat: .git/hooks/prepare-commit-msg: No such file or directory
      
      no "prepare-commit-msg" and "commit-msg" files in the build directory on b2_1 branch.
      
      $ ls build/
      Makefile			doxygen-stylesheet.css		lbuild-sles10
      Rules.in			exit_traps.sh			lbuild-sles11
      autoMakefile.am			find_linux_rpms			mptlinux.spec.patch
      autoMakefile.am.toplevel	funcs.sh			nn-check.py
      autoconf			kabi				nn-final-symbol-list.txt
      autogen.sh			lbuild				osxpack
      checkpatch.pl			lbuild-fc			patches
      checkstack.pl			lbuild-fc11			publish_doxygen
      clearpatches.sh			lbuild-fc12			quiltrc
      confirmpatches.sh		lbuild-oel5			rdac_spec
      doxyfile.api			lbuild-rhel			update_oldconfig
      doxyfile.ref			lbuild-rhel5			updatecw.sh
      doxygen-footer.html		lbuild-rhel6
      doxygen-header.html		lbuild-sles
      

      Attachments

        Activity

          People

            adilger Andreas Dilger
            ihara Shuichi Ihara (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: