From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Stephen P. Smith" Subject: [PATCH V3 0/2] specify commit by negative pattern Date: Sat, 9 Jan 2016 19:20:29 -0700 Message-ID: <1452392429-2578-1-git-send-email-ischis2@cox.net> References: Cc: Junio C Hamano , Duy Nguyen , "Stephen P. Smith" To: Git Mailing List X-From: git-owner@vger.kernel.org Sun Jan 10 03:20:05 2016 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aI5bt-0007e2-Nb for gcvg-git-2@plane.gmane.org; Sun, 10 Jan 2016 03:20:02 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756790AbcAJCT6 (ORCPT ); Sat, 9 Jan 2016 21:19:58 -0500 Received: from fed1rmfepo203.cox.net ([68.230.241.148]:43206 "EHLO fed1rmfepo203.cox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756770AbcAJCT4 (ORCPT ); Sat, 9 Jan 2016 21:19:56 -0500 Received: from fed1rmimpo305 ([68.230.241.173]) by fed1rmfepo203.cox.net (InterMail vM.8.01.05.15 201-2260-151-145-20131218) with ESMTP id <20160110021955.CHFY26406.fed1rmfepo203.cox.net@fed1rmimpo305> for ; Sat, 9 Jan 2016 21:19:55 -0500 Received: from thunderbird ([68.231.74.134]) by fed1rmimpo305 with cox id 42Ku1s00P2tqoqC012Kuw9; Sat, 09 Jan 2016 21:19:54 -0500 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020204.5691BFCA.011C,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=f8aW8pOM c=1 sm=1 a=/Rt4pg3TtX3KzfzhvVoEow==:17 a=kviXuzpPAAAA:8 a=7aQ_Q-yQQ-AA:10 a=ybZZDoGAAAAA:8 a=TSbVqHtbAAAA:8 a=0FTnuXoyAAqsf8263B0A:9 a=/Rt4pg3TtX3KzfzhvVoEow==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Received: from thunderbird.smith.home (thunderbird [127.0.0.1]) by thunderbird (Postfix) with ESMTP id C55D413F7BB; Sat, 9 Jan 2016 19:20:42 -0700 (MST) X-Mailer: git-send-email 2.7.0-rc2 In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Add support for negative pattern matching in ^{/} style revision specifiers. So now you can find the first commit whose message doesn't match a pattern, complementing the existing positive matching. e.g.: $ git rebase -i ^{/!-^WIP} My use-case is in having a "work, work, work, rebase, push"-style workflow, which generates a lot of "WIP foo" commits. While rebasing is usually handled via "git rebase -i origin/master", occasionally I will already have several "good, but not yet ready to push" commits hanging around while I finish work on related commits. In these situations, the ability to quickly "git diff ^{/!-^WIP}" to get an overview of all changes "since the last one I was happy with", can be useful. This is the second version of the patch series. The previous attempt used the notation ^{/!WIP}, rather than ^{/!-WIP}, so the "modifier" was the '!' character. Now, '!' is taken as an indicator that the pattern is to be interpreted differently, and '-' is taken as an indicator of how it is to be interpreted differently. This follows recent discussion with "Junio C Hamano" pobox.com> and much-less recent discussion archived at: http://thread.gmane.org/gmane.comp.version-control.git/40460/focus=40477 In summary, '!' is to be used as an "escape hatch", for further extension of the "name commit by pattern" functionality. Theorised future extensions indicated things like "what was to be searched", e.g.: ^{/!(a=author)}. With only two interpretations of the '!' leader, for now (including the '!!' literal notation), adding such a verbose form, such as ' ^{/!(negative)foo}', seemed inappropriate at this time. In the event that such verbose forms are ever implemented, this new form may act as a shorthand, for a basic case. Will Palmer (2): test for '!' handling in rev-parse's named commits object name: introduce '^{/!-}' notation Documentation/revisions.txt | 11 +++++----- sha1_name.c | 20 ++++++++++++----- t/t1511-rev-parse-caret.sh | 53 ++++++++++++++++++++++++++++++++++++++++++++- 3 files changed, 73 insertions(+), 11 deletions(-) -- 2.7.0-rc2