1. 20 4月, 2011 1 次提交
  2. 15 4月, 2011 3 次提交
  3. 14 4月, 2011 2 次提交
  4. 12 4月, 2011 1 次提交
  5. 07 4月, 2011 3 次提交
  6. 05 4月, 2011 2 次提交
  7. 04 4月, 2011 10 次提交
  8. 03 4月, 2011 2 次提交
  9. 02 4月, 2011 13 次提交
  10. 31 3月, 2011 3 次提交
    • J
      parse-remote: typofix · 2352570b
      Junio C Hamano 提交于
      An earlier patch had a trivial typo that two people did not notice.
      Pointed out by Michael Schubert.
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      2352570b
    • N
      submodule: process conflicting submodules only once · 313ee0d6
      Nicolas Morey-Chaisemartin 提交于
      During a merge module_list returns conflicting submodules several times
      (stage 1,2,3) which caused the submodules to be used multiple times in
      git submodule init, sync, update and status command.
      
      There are 5 callers of module_list; they all read (mode, sha1, stage,
      path) tuple, and most of them care only about path.  As a first level
      approximation, it should be Ok (in the sense that it does not make things
      worse than it currently is) to filter the duplicate paths from module_list
      output, but some callers should change their behaviour when the merge in
      the superproject still has conflicts.
      
      Notice the higher-stage entries, and emit only one record from
      module_list, but while doing so, mark the entry with "U" (not [0-3]) in
      the $stage field and null out the SHA-1 part, as the object name for the
      lowest stage does not give any useful information to the caller, and this
      way any caller that uses the object name would hopefully barf.  Then
      update the codepaths for each subcommands this way:
      
       - "update" should not touch the submodule repository, because we do not
         know what commit should be checked out yet.
      
       - "status" reports the conflicting submodules as 'U000...000' and does
         not recurse into them (we might later want to make it recurse).
      
       - The command called by "foreach" may want to do whatever it wants to do
         by noticing the merged status in the superproject itself, so feed the
         path to it from module_list as before, but only once per submodule.
      
       - "init" and "sync" are unlikely things to do while the superproject is
         still not merged, but as long as a submodule is there in $path, there
         is no point skipping it. It might however want to take the merged
         status of .gitmodules into account, but that is outside of the scope of
         this topic.
      Acked-by: NJens Lehmann <Jens.Lehmann@web.de>
      Thanks-to: Junio C Hamano <gitster@pobox.com>
      Signed-off-by: NNicolas Morey-Chaisemartin <nicolas@morey-chaisemartin.com>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      313ee0d6
    • M
      contrib/thunderbird-patch-inline: do not require bash to run the script · 806e0aba
      Maxin john 提交于
      The script does not have to be run under bash, but any POSIX compliant
      shell would do, as it does not use any bash-isms.
      
      It may be written under a different style than what is recommended in
      Documentation/CodingGuidelines, but that is a different matter.
      
      While at it, fix obvious typos in the comment.
      Signed-off-by: NMaxin B. John <maxin@maxinbjohn.info>
      Signed-off-by: NJunio C Hamano <gitster@pobox.com>
      806e0aba