1. 20 5月, 2006 4 次提交
    • S
      Log ref updates made by fetch. · d0740d92
      Shawn Pearce 提交于
      If a ref is changed by http-fetch, local-fetch or ssh-fetch
      record the change and the remote URL/name in the log for the ref.
      This requires loading the config file to check logAllRefUpdates.
      
      Also fixed a bug in the ref lock generation; the log file name was
      not being produced right due to a bad prefix length.
      Signed-off-by: NShawn O. Pearce <spearce@spearce.org>
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      d0740d92
    • S
      Force writing ref if it doesn't exist. · 732232a1
      Shawn Pearce 提交于
      Normally we try to skip writing a ref if its value hasn't changed
      but in the special case that the ref doesn't exist but the new
      value is going to be 0{40} then force writing the ref anyway.
      Signed-off-by: NShawn O. Pearce <spearce@spearce.org>
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      732232a1
    • S
      Added logs/ directory to repository layout. · c22a7f0f
      Shawn Pearce 提交于
      Signed-off-by: NShawn O. Pearce <spearce@spearce.org>
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      c22a7f0f
    • S
      General ref log reading improvements. · e5229042
      Shawn Pearce 提交于
      Corrected the log starting time displayed in the error message
      (as it was always showing the epoch due to a bad input to strtoul).
      
      Improved the log parser so we only scan backwards towards the
      '\n' from the end of the prior log; during this scan the last '>'
      is remembered to improve performance (rather than scanning forward
      to it).
      
      If the log record matched is the last log record in the file only
      use its new sha1 value if the date matches exactly; otherwise we
      leave the passed in sha1 alone as it already contains the current
      value of the ref.  This way lookups of dates later than the log
      end to stick with the current ref value in case the ref was updated
      without logging.
      
      If it looks like someone changed the ref without logging it and we
      are going to return the sha1 which should have been valid during
      the missing period then warn the user that there might be log data
      missing and thus their query result may not be accurate.  The check
      isn't perfect as its just based on comparing the old and new sha1
      values between the two log records but its better than not checking
      at all.
      
      Implemented test cases based on git-rev-parse for most of the
      boundary conditions.
      Signed-off-by: NShawn O. Pearce <spearce@spearce.org>
      Signed-off-by: NJunio C Hamano <junkio@cox.net>
      e5229042
  2. 18 5月, 2006 6 次提交
  3. 17 5月, 2006 6 次提交
  4. 16 5月, 2006 22 次提交
  5. 15 5月, 2006 2 次提交