1. 16 2月, 2011 10 次提交
  2. 15 2月, 2011 3 次提交
    • R
      configure: use AC_LANG_PROGRAM consistently · 1e58dba1
      Ralf Wildenhues 提交于
      Avoid warnings from Autoconf 2.68 about missing use of AC_LANG_PROGRAM
      and friends.
      
      Quoting autoconf-2.68/NEWS:
      
        ** The macros AC_PREPROC_IFELSE, AC_COMPILE_IFELSE, AC_LINK_IFELSE, and
           AC_RUN_IFELSE now warn if the first argument failed to use
           AC_LANG_SOURCE or AC_LANG_PROGRAM to generate the conftest file
           contents.  A new macro AC_LANG_DEFINES_PROVIDED exists if you have
           a compelling reason why you cannot use AC_LANG_SOURCE but must
           avoid the warning.
      
      The underlying reason for that change is that AC_LANG_{SOURCE,PROGRAM}
      take care to supply the previously computed set of #defines (and
      include standard headers if so desired) for preprocessed languages
      like C and C++.
      
      In some cases, AC_LANG_PROGRAM is already used but not sufficiently
      m4-quoted, so we just need to add another set of [quotes] to prevent
      the autoconf warning from being triggered bogusly.  Quoting all
      arguments (except when calling special macros that need to be expanded
      before recursion) is better style, anyway.  These and more rules are
      described in detail in 'info Autoconf "Programming in M4"'.
      
      No change in the resulting config.mak.autogen after running
      ./configure intended.
      Signed-off-by: NRalf Wildenhues <Ralf.Wildenhues@gmx.de>
      Signed-off-by: NJonathan Nieder <jrnieder@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      1e58dba1
    • J
      string_list_append: always set util pointer to NULL · 62b8102c
      Jeff King 提交于
      It is not immediately obvious that the util field may
      contain random bytes after appending an item. Especially
      since the string_list_insert* functions _do_ explicitly zero
      the util pointer.
      
      This does not appear to be a bug in any current git code, as
      all callers either fill in the util field immediately or
      never use it. However, it is worth it to be less surprising
      to new users of the string-list API who may expect it to be
      intialized to NULL.
      Signed-off-by: NJeff King <peff@peff.net>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      62b8102c
    • J
      correct type of EMPTY_TREE_SHA1_BIN · dab0d410
      Jonathan Nieder 提交于
      Functions such as hashcmp that expect a binary SHA-1 value take
      parameters of type "unsigned char *" to avoid accepting a textual
      SHA-1 passed by mistake.  Unfortunately, this means passing the string
      literal EMPTY_TREE_SHA1_BIN requires an ugly cast.  Tweak the
      definition of EMPTY_TREE_SHA1_BIN to produce a value of more
      convenient type.
      
      In the future the definition might change to
      
      	extern const unsigned char empty_tree_sha1_bin[20];
      	#define EMPTY_TREE_SHA1_BIN empty_tree_sha1_bin
      Signed-off-by: NJonathan Nieder <jrnieder@gmail.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      dab0d410
  3. 12 2月, 2011 4 次提交
  4. 11 2月, 2011 1 次提交
  5. 10 2月, 2011 4 次提交
  6. 08 2月, 2011 12 次提交
  7. 07 2月, 2011 1 次提交
  8. 01 2月, 2011 2 次提交
  9. 31 1月, 2011 1 次提交
  10. 28 1月, 2011 2 次提交