Permalink
Switch branches/tags
Nothing to show
Commits on Aug 27, 2016
  1. end on master

    committed Aug 27, 2016
  2. more utils

    committed Aug 27, 2016
  3. add cleanup

    committed Aug 27, 2016
Commits on Apr 23, 2016
  1. Merge pull request #23 from Tzrlk/master

    Added the option of stashing untracked and ignored files on switch.
    committed Apr 23, 2016
  2. in sync if merge squash

    committed Apr 23, 2016
Commits on Oct 1, 2015
Commits on Dec 12, 2014
Commits on Sep 15, 2014
  1. fix addremove

    committed Sep 15, 2014
Commits on Dec 28, 2012
  1. Merge pull request #20 from phoenixsong6/unwip

    unwip: check previous commit
    committed Dec 28, 2012
  2. unwip: check previous commit

    Closes #15
    e-nomem committed Dec 28, 2012
Commits on Jun 18, 2012
  1. Merge pull request #18 from brantb/master

    git-wtf: Change delimiter of `git log --pretty` format string to |.
    committed Jun 18, 2012
Commits on Jun 15, 2012
  1. git-wtf: Change delimiter of `git log --pretty` format string to |.

    This prevents e-mail addresses with dashes in them from mangling the
    output of the command. | is a safer character than , because it cannot
    appear in e-mail addresses or commit IDs.
    brantb committed Jun 15, 2012
Commits on Jan 27, 2012
  1. Merge pull request #14 from korishev/master

    make git-wtf handle branches with a '/' in them
    committed Jan 27, 2012
  2. update git-wtf to handle branches with '/' in them, like git-flow 'fe…

    …ature/feature-name' branches
    korishev committed Jan 27, 2012
Commits on Dec 6, 2011
  1. Merge pull request #13 from simplybusiness/git_last_number_of_commits

    Use 1 as the default number of commits (git last)
    committed Dec 6, 2011
Commits on Dec 5, 2011
  1. Use 1 as the default number of commits (git last)

    This patch sets the default number of commits to 1, in case
    no number of commits is specified on the command line (note
    that this requires the bash shell, as it uses bash-specific
    shell parameter expansion syntax)... avoiding the following
    error message:
    
    ~ $ git last
    error: -n requires an argument
    ~ $ git-last
    error: -n requires an argument
    ~ $ _
    pvdb committed Dec 5, 2011
Commits on Oct 19, 2011
  1. Merge pull request #10 from davejamesmiller/master

    git-incoming/outgoing require bash
    committed Oct 19, 2011
Commits on Jul 22, 2011
  1. Merge pull request #6 from simplybusiness/gitflow_support

    Support gitflow-style branch names (with embedded "/")
    committed Jul 22, 2011
  2. Support gitflow-style branch names (with embedded "/")

    gitflow - https://github.com/nvie/gitflow - by default uses
    branch prefixes that include a slash ("/") as illustrated by
    the following default settings:
    
        gitflow.prefix.feature=feature/
        gitflow.prefix.release=release/
        gitflow.prefix.hotfix=hotfix/
        gitflow.prefix.support=support/
    
    This causes git-incoming and git-outgoing to stop working, though,
    as they both make the implicit assumption that branch names do not
    have an embedded "/".
    
    This pull request removes that implicit assumption, and ensures
    that both scripts work properly for git repos that have gitflow
    style branch names.
    pvdb committed Jul 22, 2011
Commits on Jun 21, 2011
  1. python not python2

    committed Jun 21, 2011
  2. update README

    committed Jun 21, 2011
  3. add git-pull-request

    committed Jun 21, 2011
Commits on Dec 2, 2010
  1. re-add git-switch

    committed Dec 2, 2010
Commits on Aug 31, 2010
  1. remove git utils i havent used

    committed Aug 31, 2010
Commits on Jun 3, 2010
  1. Revert "Better behavior if nothing is to be added/removed (no 'git rm…

    …' help output as before). I believe the 'git add' now is more clear, is there any drawback because of this change ? I think that there it isn't."
    
    This commit did not work on OSX.
    
    This reverts commit a79557f.
    committed Jun 3, 2010
Commits on Apr 9, 2010
Commits on Dec 17, 2009
  1. Better behavior if nothing is to be added/removed (no 'git rm' help o…

    …utput as before). I believe the 'git add' now is more clear, is there any drawback because of this change ? I think that there it isn't.
    ereslibre committed with Dec 15, 2009
Commits on Oct 19, 2009
  1. get rid of debugging print

    committed Oct 19, 2009
  2. get rid of debugging print

    committed Oct 19, 2009
  3. better alts

    committed Oct 19, 2009
  4. more accurate wtf

    committed Oct 19, 2009