1. 22 Mar, 2010 1 commit
  2. 18 Mar, 2010 1 commit
    • Ryan Jackson's avatar
      Fix gitmail's short_refname() to support refs containing slashes · b3943c83
      Ryan Jackson authored
      Refs can contain slashes.  For example, the short ref for
      'refs/heads/foo/bar' is 'foo/bar'.  Previously, we just chopped off
      everything up to and including the last slash character, which doesn't
      return the correct short ref in this case.
      
      Call git-rev-parse to shorten the ref for us.  In case it doesn't return
      anything (which shouldn't happen), fall back to the full ref.
      b3943c83
  3. 03 Feb, 2010 1 commit
    • Ryan Jackson's avatar
      Add support for forced updates (incl. rebases) · d3a1ba3a
      Ryan Jackson authored
      Handle forced updates, including rebases.  git-cherry is used to
      determine if the commits pushed are present upstream (with a different
      hash) or not.  Ones already present are excluded from the commit mail
      since they haven't changed (i.e., they point to the same blobs the old
      ones did).  Ones not present are either new commits or modified commits.
      It's non-trivial to tell which is which, and we probably don't care
      anyway.  Added text to 'forced-update' email messages to state that the
      commits shown are only the new/modified ones and not all that were
      pushed.
      d3a1ba3a
  4. 02 Feb, 2010 1 commit
  5. 01 Feb, 2010 2 commits
  6. 22 Jan, 2010 1 commit
  7. 21 Jan, 2010 1 commit
  8. 19 Jan, 2010 2 commits
  9. 23 Dec, 2009 4 commits
  10. 22 Dec, 2009 2 commits
  11. 21 Dec, 2009 3 commits
    • Robert Ricci's avatar
      Change the mail and branch matching code due to a conversation I had · 46157519
      Robert Ricci authored
      with Eric this afternoon.
      46157519
    • Ryan Jackson's avatar
      Add helper scripts to make exporting to CVS easier · facfd08e
      Ryan Jackson authored
      - git-cvsexportcommit.mod is the same as the standard
        git-cvsexportcommit script, except it doesn't fail if you try applying
        a patch to the sandbox that has already been applied (i.e., you do a
        cvspush before the upstream git repo has been updated).
      
      - git-cvspush uses the above script to export each commit between the
        upstream branch head and your local branch head to CVS. To use it,
        run the following command inside your git repo:
      
        git config branch.<branch>.cvsdir <sandbox>
      
        where '<branch>' is your local git branch name and '<sandbox>' is
        the CVS sandbox where you've checked out that branch.  Set up an
        alias for it with this:
      
        git config --global alias.cvspush "!git-cvspush"
      
        and run 'git cvspush <branch>' (where '<branch>' is the branch to push
        or the current one if not specified) when you're ready to push pending
        commits to CVS.
      facfd08e
    • Robert Ricci's avatar
      New script: gitmail . Will be used to send out mail about git pushes · bcd94a3b
      Robert Ricci authored
      to mailing lists, etc.
      bcd94a3b