1. 14 12月, 2005 6 次提交
    • F
      Usage message clean-up, take #2 · d025524d
      Fredrik Kuivinen 提交于
      There were some problems with the usage message clean-up patch
      series. I hadn't realised that subdirectory aware scripts can't source
      git-sh-setup. I propose that we change this and let the scripts which
      are subdirectory aware set a variable, SUBDIRECTORY_OK, before they
      source git-sh-setup.
      
      The scripts will also set USAGE and possibly LONG_USAGE before they
      source git-sh-setup. If LONG_USAGE isn't set it defaults to USAGE.
      
      If we go this way it's easy to catch --help in git-sh-setup, print the
      (long) usage message to stdout and exit cleanly. git-sh-setup can
      define a 'usage' shell function which can be called by the scripts to
      print the short usage string to stderr and exit non-cleanly. It will
      also be easy to change $0 to basename $0 or something else, if would
      like to do that sometime in the future.
      
      What follows is a patch to convert a couple of the commands to this
      style. If it's ok with everyone to do it this way I will convert the
      rest of the scripts too.
      
      [jc: thrown in to proposed updates queue for comments.]
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      d025524d
    • J
      Everyday: a bit more examples. · 01f49e34
      Junio C Hamano 提交于
      Talk about the following as well:
      
       * git fetch --tags
       * Use of "git push" as a one-man distributed development vehicle.
       * Show example of remotes file for pulling and pushing.
       * Annotate git-shell setup.
       * Using Carl's update hook in a CVS-style shared repository.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      01f49e34
    • J
      checkout-index: fix checking out specific path. · f4f9adae
      Junio C Hamano 提交于
      3bd348ae commit broke checking
      out specific paths.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      f4f9adae
    • P
      Make git-send-pack exit with error when some refs couldn't be pushed out · ed24928e
      Petr Baudis 提交于
      In case some refs couldn't be pushed out due to an error (mostly the
      not-a-proper-subset error), make git-send-pack exit with non-zero status
      after the push is over (that is, it still tries to push out the rest
      of the refs).
      
      [jc: I adjusted a test for this change.]
      Signed-off-by: NPetr Baudis <pasky@suse.cz>
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      ed24928e
    • J
      [PATCH] allow merging any committish · 9954f5b8
      Junio C Hamano 提交于
      Although "git-merge" is advertised as the end-user level command
      (instead of being a "git-pull" backend), it was not prepared to
      take tag objects that point at commits and barfed when fed one.
      Sanitize the input while we validate them, for which we already
      have a loop.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      9954f5b8
    • J
      git-clone: tell the user a bit more about clone-pack failure. · 0a8b4def
      Junio C Hamano 提交于
      When clone-pack has trouble with the remote, it dies unfriendly
      "EOF" error message.  We cannot tell the reason why it failed
      from the local end; it could be that the repository did not
      exist, or configured not to serve over git-daemon, or a network
      failure.  At least, saying clone-pack failed makes it a bit more
      meaningful.
      
      I am not convinced yet that removing the newly created directory
      is the right thing to do, so this commit leaves the new
      directory behind.
      
      Reported by Sam Ravnborg.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      0a8b4def
  2. 13 12月, 2005 12 次提交
  3. 12 12月, 2005 1 次提交
    • J
      t/t6022: a new test for renaming merge. · b825e6ff
      Junio C Hamano 提交于
      This adds a couple of tests to cover the following renaming
      merge cases:
      
       - one side renames and the other side does not, with and without
         content conflicts.
      
       - both side rename to the same path, with and without content
         conflicts.
      
      The test setup also prepares a case in which both side rename to
      different destination, but currently the code collapses these
      destination paths and removes the original path, which may be
      wrong.  The outcome of this case is not checked by the tests in
      this round.
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      b825e6ff
  4. 11 12月, 2005 15 次提交
  5. 10 12月, 2005 4 次提交
  6. 09 12月, 2005 2 次提交