summaryrefslogtreecommitdiff
path: root/t/t4129-apply-samemode.sh
diff options
context:
space:
mode:
authorLibravatar Will Palmer <wmpalmer@gmail.com>2016-01-30 17:06:01 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2016-02-01 13:40:37 -0800
commit0769854f3db2c09c8b5993ea023ea07ddc1eb6eb (patch)
tree335f735c80d71a956c2ae4e46127043cd66315bf /t/t4129-apply-samemode.sh
parenttest for '!' handling in rev-parse's named commits (diff)
downloadtgif-0769854f3db2c09c8b5993ea023ea07ddc1eb6eb.tar.xz
object name: introduce '^{/!-<negative pattern>}' notation
To name a commit, you can now use the :/!-<negative pattern> regex style, and consequentially, say $ git rev-parse HEAD^{/!-foo} and it will return the hash of the first commit reachable from HEAD, whose commit message does not contain "foo". This is the opposite of the existing <rev>^{/<pattern>} syntax. The specific use-case this is intended for is to perform an operation, excluding the most-recent commits containing a particular marker. For example, if you tend to make "work in progress" commits, with messages beginning with "WIP", you work, then it could be useful to diff against "the most recent commit which was not a WIP commit". That sort of thing now possible, via commands such as: $ git diff @^{/!-^WIP} The leader '/!-', rather than simply '/!', to denote a negative match, is chosen to leave room for additional modifiers in the future. Signed-off-by: Will Palmer <wmpalmer@gmail.com> Signed-off-by: Stephen P. Smith <ischis2@cox.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4129-apply-samemode.sh')
0 files changed, 0 insertions, 0 deletions