git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Stefan Beller <sbeller@google.com>
To: git@vger.kernel.org, gitster@pobox.com
Cc: Stefan Beller <sbeller@google.com>,
	pclouds@gmail.com, sunshine@sunshineco.com
Subject: [PATCH 0/2] Remove get_pathspec finally
Date: Thu,  6 Aug 2015 11:27:10 -0700	[thread overview]
Message-ID: <1438885632-26470-1-git-send-email-sbeller@google.com> (raw)
In-Reply-To: <CAPig+cT_YB=HY9dBo5eRNu4qvCqCXRwwXgpxCA8YjxagP+sHfA@mail.gmail.com>

Remove the last caller of the get_pathspec function and the get_pathspec function
itself.

I stumbled into this as I was reading the documentation on pathspec, and the
first sentence

  get_pathspec() is obsolete and should never be used in new code.

made me wonder.

This replaces sb/remove-get-pathspec

Stefan Beller (2):
  builtin/mv: remove get_pathspec()
  pathspec: remove deprecated get_pathspec

 Documentation/technical/api-setup.txt |  2 --
 builtin/mv.c                          | 16 +++++++++++++---
 cache.h                               |  1 -
 pathspec.c                            | 36 -----------------------------------
 pathspec.h                            |  2 +-
 5 files changed, 14 insertions(+), 43 deletions(-)

-- 
2.5.0.239.g9728e1d.dirty

  reply	other threads:[~2015-08-06 18:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-03 17:53 [PATCH] builtin/mv: Get rid of the last caller of get_pathspec Stefan Beller
2015-08-03 22:48 ` Eric Sunshine
2015-08-06 18:27   ` Stefan Beller [this message]
2015-08-06 18:27     ` [PATCH 1/2] builtin/mv: remove get_pathspec() Stefan Beller
2015-08-06 18:46       ` Eric Sunshine
2015-08-06 18:58         ` Stefan Beller
2015-08-06 20:18           ` Eric Sunshine
2015-08-06 20:59             ` Stefan Beller
2015-08-06 18:27     ` [PATCH 2/2] pathspec: remove deprecated get_pathspec Stefan Beller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1438885632-26470-1-git-send-email-sbeller@google.com \
    --to=sbeller@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pclouds@gmail.com \
    --cc=sunshine@sunshineco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).