1. 03 3月, 2007 1 次提交
    • J
      Add core.symlinks to mark filesystems that do not support symbolic links. · 78a8d641
      Johannes Sixt 提交于
      Some file systems that can host git repositories and their working copies
      do not support symbolic links. But then if the repository contains a symbolic
      link, it is impossible to check out the working copy.
      
      This patch enables partial support of symbolic links so that it is possible
      to check out a working copy on such a file system.  A new flag
      core.symlinks (which is true by default) can be set to false to indicate
      that the filesystem does not support symbolic links. In this case, symbolic
      links that exist in the trees are checked out as small plain files, and
      checking in modifications of these files preserve the symlink property in
      the database (as long as an entry exists in the index).
      
      Of course, this does not magically make symbolic links work on such defective
      file systems; hence, this solution does not help if the working copy relies
      on that an entry is a real symbolic link.
      Signed-off-by: NJohannes Sixt <johannes.sixt@telecom.at>
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      78a8d641
  2. 29 1月, 2007 1 次提交
  3. 19 1月, 2007 1 次提交
  4. 13 11月, 2006 1 次提交
  5. 24 8月, 2006 1 次提交
  6. 04 6月, 2006 1 次提交
  7. 06 5月, 2006 2 次提交
  8. 04 5月, 2006 2 次提交
  9. 29 4月, 2006 1 次提交
  10. 12 2月, 2006 1 次提交
  11. 07 12月, 2005 1 次提交
    • J
      update-index: allow --index-info to add higher stages. · d23748a6
      Junio C Hamano 提交于
      The new merge world order tells the merge strategies to leave
      the cache unmerged and store the automerge result in the working
      tree if automerge is not clean.  This was done for the resolve
      strategy and recursive strategy when no rename is involved, but
      recording a conflicting merge in the rename case could not
      easily be done by the recursive strategy.
      
      This commit adds a new input format, in addition to the exsting
      two, to "update-index --index-info".
      
          (1) mode         SP sha1          TAB path
          The first format is what "git-apply --index-info"
          reports, and used to reconstruct a partial tree
          that is used for phony merge base tree when falling
          back on 3-way merge.
      
          (2) mode SP type SP sha1          TAB path
          The second format is to stuff git-ls-tree output
          into the index file.
      
          (3) mode         SP sha1 SP stage TAB path
          This format is to put higher order stages into the
          index file and matches git-ls-files --stage output.
      
      To place a higher stage entry to the index, the path should
      first be removed by feeding a mode=0 entry for the path, and
      then feeding necessary input lines in the (3) format.
      
      For example, starting with this index:
      
      $ git ls-files -s
      100644 8a1218a1024a212bb3db30becd860315f9f3ac52 0       frotz
      
      $ git update-index --index-info ;# interactive session -- input follows...
      
      0 0000000000000000000000000000000000000000	frotz
      100644 8a1218a1024a212bb3db30becd860315f9f3ac52 1	frotz
      100755 8a1218a1024a212bb3db30becd860315f9f3ac52 2	frotz
      
      The first line of the input feeds 0 as the mode to remove the
      path; the SHA1 does not matter as long as it is well formatted.
      Then the second and third line feeds stage 1 and stage 2 entries
      for that path.  After the above, we would end up with this:
      
      $ git ls-files -s
      100644 8a1218a1024a212bb3db30becd860315f9f3ac52 1	frotz
      100755 8a1218a1024a212bb3db30becd860315f9f3ac52 2	frotz
      
      This completes the groundwork for the new merge world order.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      d23748a6
  12. 06 12月, 2005 1 次提交
  13. 15 11月, 2005 1 次提交
  14. 12 11月, 2005 1 次提交
  15. 31 10月, 2005 1 次提交
  16. 30 10月, 2005 1 次提交
  17. 04 10月, 2005 1 次提交
    • J
      [PATCH] Random documentation fixes · df8baa42
      Jonas Fonseca 提交于
      The fixes focuses on improving the HTML output. Most noteworthy:
      
       - Fix the Makefile to also make various *.html files depend on
         included files.
      
       - Consistently use 'NOTE: ...' instead of '[ ... ]' for additional
         info.
      
       - Fix ending '::' for description lists in OPTION section etc.
      
       - Fix paragraphs in description lists ending up as preformated text.
      
       - Always use listingblocks (preformatted text wrapped in lines with -----)
         for examples that span empty lines, so they are put in only one HTML
         block.
      
       - Use '1.' instead of '(1)' for numbered lists.
      
       - Fix linking to other GIT docs.
      
       - git-rev-list.txt: put option descriptions in an OPTION section.
      Signed-off-by: NJonas Fonseca <fonseca@diku.dk>
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      df8baa42
  18. 28 9月, 2005 1 次提交
  19. 21 9月, 2005 1 次提交
  20. 08 9月, 2005 1 次提交
    • J
      Big tool rename. · 215a7ad1
      Junio C Hamano 提交于
      As promised, this is the "big tool rename" patch.  The primary differences
      since 0.99.6 are:
      
        (1) git-*-script are no more.  The commands installed do not
            have any such suffix so users do not have to remember if
            something is implemented as a shell script or not.
      
        (2) Many command names with 'cache' in them are renamed with
            'index' if that is what they mean.
      
      There are backward compatibility symblic links so that you and
      Porcelains can keep using the old names, but the backward
      compatibility support  is expected to be removed in the near
      future.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      215a7ad1
  21. 09 7月, 2005 1 次提交
  22. 06 6月, 2005 1 次提交
  23. 11 5月, 2005 1 次提交