Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Aug 30, 2010
  1. @gitster

    object.h: Add OBJECT_ARRAY_INIT macro and make use of it.

    Thiago Farina authored gitster committed
    Signed-off-by: Thiago Farina <tfransosi@gmail.com>
    Signed-off-by: Junio C Hamano <gitster@pobox.com>
Commits on Feb 19, 2008
  1. @gitster

    Merge branch 'mk/maint-parse-careful'

    gitster authored
    * mk/maint-parse-careful:
      peel_onion: handle NULL
      check return value from parse_commit() in various functions
      parse_commit: don't fail, if object is NULL
      revision.c: handle tag->tagged == NULL
      reachable.c::process_tree/blob: check for NULL
      process_tag: handle tag->tagged == NULL
      check results of parse_commit in merge_bases
      list-objects.c::process_tree/blob: check for NULL
      reachable.c::add_one_tree: handle NULL from lookup_tree
      mark_blob/tree_uninteresting: check for NULL
      get_sha1_oneline: check return value of parse_object
      read_object_with_reference: don't read beyond the buffer
  2. @gitster

    check return value from parse_commit() in various functions

    Martin Koegler authored gitster committed
    Signed-off-by: Martin Koegler <mkoegler@auto.tuwien.ac.at>
    Signed-off-by: Junio C Hamano <gitster@pobox.com>
Commits on Feb 18, 2008
  1. @gitster

    deref_tag: handle return value NULL

    Martin Koegler authored gitster committed
    Signed-off-by: Martin Koegler <mkoegler@auto.tuwien.ac.at>
    Signed-off-by: Junio C Hamano <gitster@pobox.com>
Commits on Jun 7, 2007
  1. @gitster

    War on whitespace

    gitster authored
    This uses "git-apply --whitespace=strip" to fix whitespace errors that have
    crept in to our source files over time.  There are a few files that need
    to have trailing whitespaces (most notably, test vectors).  The results
    still passes the test, and build result in Documentation/ area is unchanged.
    
    Signed-off-by: Junio C Hamano <gitster@pobox.com>
Commits on Jan 22, 2007
  1. is_repository_shallow(): prototype fix.

    Junio C Hamano authored
    Signed-off-by: Junio C Hamano <junkio@cox.net>
Commits on Nov 24, 2006
  1. @julliard

    get_shallow_commits: Avoid memory leak if a commit has been reached a…

    julliard authored Junio C Hamano committed
    …lready.
    
    Signed-off-by: Alexandre Julliard <julliard@winehq.org>
    Signed-off-by: Junio C Hamano <junkio@cox.net>
  2. @julliard

    Shallow clone: do not ignore shallowness when following tags

    julliard authored Junio C Hamano committed
    Tags should be considered when truncating the
    commit list. The patch below fixes it, and fetches the right number of
    commits for each tag. However the correct fix is probably to not fetch
    historical tags at all.
    
    Signed-off-by: Junio C Hamano <junkio@cox.net>
  3. @dscho

    allow deepening of a shallow repository

    dscho authored Junio C Hamano committed
    Now, by saying "git fetch -depth <n> <repo>" you can deepen
    a shallow repository.
    
    Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
    Signed-off-by: Junio C Hamano <junkio@cox.net>
  4. @dscho

    support fetching into a shallow repository

    dscho authored Junio C Hamano committed
    A shallow commit is a commit which has parents, which in turn are
    "grafted away", i.e. the commit appears as if it were a root.
    
    Since these shallow commits should not be edited by the user, but
    only by core git, they are recorded in the file $GIT_DIR/shallow.
    
    A repository containing shallow commits is called shallow.
    
    The advantage of a shallow repository is that even if the upstream
    contains lots of history, your local (shallow) repository needs not
    occupy much disk space.
    
    The disadvantage is that you might miss a merge base when pulling
    some remote branch.
    
    Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
    Signed-off-by: Junio C Hamano <junkio@cox.net>
Something went wrong with that request. Please try again.