new addition

.venv/Lib/site-packages/git_filter_repo-2.47.0.dist-info/COPYING

@@ -0,0 +1,23 @@
+git-filter-repo itself and most the files in this repository (exceptions
+noted below) are provided under the MIT license (see COPYING.mit).
+
+The usage of the MIT license probably makes filter-repo compatible with
+everything, but just in case, these files can also be used under whatever
+open source license[1] that git.git or libgit2 use now or in the future
+(currently GPL[2] and GPL-with-linking-exception[3]).  Further, the
+examples (in contrib/filter-repo-demos/ and t/t9391/) can also be used
+under the same license that libgit2 provides their examples under (CC0,
+currently[4]).
+
+Exceptions:
+
+  - The test harness (t/test-lib.sh, t/test-lib-functions.sh) is a slightly
+    modified copy of git.git's test harness (the difference being that my
+    copy doesn't require a built version of 'git' to be present).  These
+    are thus GPL2 (see COPYING.gpl), and are individually marked as such.
+
+
+[1] ...as defined by the Open Source Initiative (https://opensource.org/)
+[2] https://git.kernel.org/pub/scm/git/git.git/tree/COPYING
+[3] https://github.com/libgit2/libgit2/blob/master/COPYING
+[4] https://github.com/libgit2/libgit2/blob/master/examples/COPYING

.venv/Lib/site-packages/git_filter_repo-2.47.0.dist-info/COPYING.gpl

@@ -0,0 +1,339 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+                            NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License along
+    with this program; if not, write to the Free Software Foundation, Inc.,
+    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.

.venv/Lib/site-packages/git_filter_repo-2.47.0.dist-info/COPYING.mit

@@ -0,0 +1,19 @@
+Copyright (c) 2009, 2018-2019
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

.venv/Lib/site-packages/git_filter_repo-2.47.0.dist-info/INSTALLER

@@ -0,0 +1 @@
+pip

.venv/Lib/site-packages/git_filter_repo-2.47.0.dist-info/METADATA

@@ -0,0 +1,607 @@
+Metadata-Version: 2.1
+Name: git-filter-repo
+Version: 2.47.0
+Summary: Quickly rewrite git repository history
+Author-email: Elijah Newren <[email protected]>
+License: MIT
+Project-URL: Homepage, https://github.com/newren/git-filter-repo
+Project-URL: Issues, https://github.com/newren/git-filter-repo/issues/
+Project-URL: Source, https://github.com/newren/git-filter-repo
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3.6
+Classifier: Programming Language :: Python :: 3.7
+Classifier: Programming Language :: Python :: 3.8
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: Implementation :: CPython
+Classifier: Programming Language :: Python :: Implementation :: PyPy
+Requires-Python: >=3.6
+Description-Content-Type: text/markdown
+License-File: COPYING
+License-File: COPYING.gpl
+License-File: COPYING.mit
+
+git filter-repo is a versatile tool for rewriting history, which includes
+[capabilities I have not found anywhere
+else](#design-rationale-behind-filter-repo).  It roughly falls into the
+same space of tool as [git
+filter-branch](https://git-scm.com/docs/git-filter-branch) but without the
+capitulation-inducing poor
+[performance](https://public-inbox.org/git/CABPp-BGOz8nks0+Tdw5GyGqxeYR-3FF6FT5JcgVqZDYVRQ6qog@mail.gmail.com/),
+with far more capabilities, and with a design that scales usability-wise
+beyond trivial rewriting cases.  [git filter-repo is now recommended by the
+git project](https://git-scm.com/docs/git-filter-branch#_warning) instead
+of git filter-branch.
+
+While most users will probably just use filter-repo as a simple command
+line tool (and likely only use a few of its flags), at its core filter-repo
+contains a library for creating history rewriting tools.  As such, users
+with specialized needs can leverage it to quickly create [entirely new
+history rewriting tools](contrib/filter-repo-demos).
+
+# Table of Contents
+
+  * [Prerequisites](#prerequisites)
+  * [How do I install it?](#how-do-i-install-it)
+  * [How do I use it?](#how-do-i-use-it)
+  * [Why filter-repo instead of other alternatives?](#why-filter-repo-instead-of-other-alternatives)
+    * [filter-branch](#filter-branch)
+    * [BFG Repo Cleaner](#bfg-repo-cleaner)
+  * [Simple example, with comparisons](#simple-example-with-comparisons)
+    * [Solving this with filter-repo](#solving-this-with-filter-repo)
+    * [Solving this with BFG Repo Cleaner](#solving-this-with-bfg-repo-cleaner)
+    * [Solving this with filter-branch](#solving-this-with-filter-branch)
+    * [Solving this with fast-export/fast-import](#solving-this-with-fast-exportfast-import)
+  * [Design rationale behind filter-repo](#design-rationale-behind-filter-repo)
+  * [How do I contribute?](#how-do-i-contribute)
+  * [Is there a Code of Conduct?](#is-there-a-code-of-conduct)
+  * [Upstream Improvements](#upstream-improvements)
+
+# Prerequisites
+
+filter-repo requires:
+
+  * git >= 2.22.0 at a minimum; [some features](#upstream-improvements)
+    require git >= 2.24.0 or later
+  * python3 >= 3.6
+
+# How do I install it?
+
+While the `git-filter-repo` repository has many files, the main logic
+is all contained in a single-file python script named
+`git-filter-repo`, which was done to make installation for basic use
+on many systems trivial: just place that one file into your $PATH.
+
+See [INSTALL.md](INSTALL.md) for things beyond basic usage or special
+cases.  The more involved instructions are only needed if one of the
+following apply:
+
+  * you do not find the above comment about trivial installation intuitively
+    obvious
+  * you are working with a python3 executable named something other than
+    "python3"
+  * you want to install documentation (beyond the builtin docs shown with -h)
+  * you want to run some of the [contrib](contrib/filter-repo-demos/) examples
+  * you want to create your own python filtering scripts using filter-repo as
+    a module/library
+
+# How do I use it?
+
+For comprehensive documentation:
+  * see the [user manual](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html)
+  * alternative formating of the user manual is available on various
+    external sites
+    ([example](https://www.mankier.com/1/git-filter-repo)), for those
+    that don't like the htmlpreview.github.io layout, though it may
+    only be up-to-date as of the latest release
+
+If you prefer learning from examples:
+  * there is a [cheat sheet for converting filter-branch
+    commands](Documentation/converting-from-filter-branch.md#cheat-sheet-conversion-of-examples-from-the-filter-branch-manpage),
+    which covers every example from the filter-branch manual
+  * there is a [cheat sheet for converting BFG Repo Cleaner
+    commands](Documentation/converting-from-bfg-repo-cleaner.md#cheat-sheet-conversion-of-examples-from-bfg),
+    which covers every example from the BFG website
+  * the [simple example](#simple-example-with-comparisons) below may
+    be of interest
+  * the user manual has an extensive [examples
+section](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html#EXAMPLES)
+  * I have collected a set of [example filterings based on user-filed issues](Documentation/examples-from-user-filed-issues.md)
+
+In either case, you may also find the [Frequently Answered Questions](Documentation/FAQ.md) useful.
+
+# Why filter-repo instead of other alternatives?
+
+This was covered in more detail in a [Git Rev News article on
+filter-repo](https://git.github.io/rev_news/2019/08/21/edition-54/#an-introduction-to-git-filter-repo--written-by-elijah-newren),
+but some highlights for the main competitors:
+
+## filter-branch
+
+  * filter-branch is [extremely to unusably
+    slow](https://public-inbox.org/git/CABPp-BGOz8nks0+Tdw5GyGqxeYR-3FF6FT5JcgVqZDYVRQ6qog@mail.gmail.com/)
+    ([multiple orders of magnitude slower than it should
+    be](https://git-scm.com/docs/git-filter-branch#PERFORMANCE))
+    for non-trivial repositories.
+
+  * [filter-branch is riddled with
+    gotchas](https://git-scm.com/docs/git-filter-branch#SAFETY) that can
+    silently corrupt your rewrite or at least thwart your "cleanup"
+    efforts by giving you something more problematic and messy than what
+    you started with.
+
+  * filter-branch is [very onerous](#simple-example-with-comparisons)
+    [to
+    use](https://github.com/newren/git-filter-repo/blob/a6a6a1b0f62d365bbe2e76f823e1621857ec4dbd/contrib/filter-repo-demos/filter-lamely#L9-L61)
+    for any rewrite which is even slightly non-trivial.
+
+  * the git project has stated that the above issues with filter-branch
+    cannot be backward compatibly fixed; they recommend that you [stop
+    using
+    filter-branch](https://git-scm.com/docs/git-filter-branch#_warning)
+
+  * die-hard fans of filter-branch may be interested in
+    [filter-lamely](contrib/filter-repo-demos/filter-lamely)
+    (a.k.a. [filter-branch-ish](contrib/filter-repo-demos/filter-branch-ish)),
+    a reimplementation of filter-branch based on filter-repo which is
+    more performant (though not nearly as fast or safe as
+    filter-repo).
+
+  * a [cheat
+    sheet](Documentation/converting-from-filter-branch.md#cheat-sheet-conversion-of-examples-from-the-filter-branch-manpage)
+    is available showing how to convert example commands from the manual of
+    filter-branch into filter-repo commands.
+
+## BFG Repo Cleaner
+
+  * great tool for its time, but while it makes some things simple, it
+    is limited to a few kinds of rewrites.
+
+  * its architecture is not amenable to handling more types of
+    rewrites.
+
+  * its architecture presents some shortcomings and bugs even for its
+    intended usecase.
+
+  * fans of bfg may be interested in
+    [bfg-ish](contrib/filter-repo-demos/bfg-ish), a reimplementation of bfg
+    based on filter-repo which includes several new features and bugfixes
+    relative to bfg.
+
+  * a [cheat
+    sheet](Documentation/converting-from-bfg-repo-cleaner.md#cheat-sheet-conversion-of-examples-from-bfg)
+    is available showing how to convert example commands from the manual of
+    BFG Repo Cleaner into filter-repo commands.
+
+# Simple example, with comparisons
+
+Let's say that we want to extract a piece of a repository, with the intent
+on merging just that piece into some other bigger repo.  For extraction, we
+want to:
+
+  * extract the history of a single directory, src/.  This means that only
+    paths under src/ remain in the repo, and any commits that only touched
+    paths outside this directory will be removed.
+  * rename all files to have a new leading directory, my-module/ (e.g. so that
+    src/foo.c becomes my-module/src/foo.c)
+  * rename any tags in the extracted repository to have a 'my-module-'
+    prefix (to avoid any conflicts when we later merge this repo into
+    something else)
+
+## Solving this with filter-repo
+
+Doing this with filter-repo is as simple as the following command:
+```shell
+  git filter-repo --path src/ --to-subdirectory-filter my-module --tag-rename '':'my-module-'
+```
+(the single quotes are unnecessary, but make it clearer to a human that we
+are replacing the empty string as a prefix with `my-module-`)
+
+## Solving this with BFG Repo Cleaner
+
+BFG Repo Cleaner is not capable of this kind of rewrite; in fact, all
+three types of wanted changes are outside of its capabilities.
+
+## Solving this with filter-branch
+
+filter-branch comes with a pile of caveats (more on that below) even
+once you figure out the necessary invocation(s):
+
+```shell
+  git filter-branch \
+      --tree-filter 'mkdir -p my-module && \
+                     git ls-files \
+                         | grep -v ^src/ \
+                         | xargs git rm -f -q && \
+                     ls -d * \
+                         | grep -v my-module \
+                         | xargs -I files mv files my-module/' \
+          --tag-name-filter 'echo "my-module-$(cat)"' \
+	  --prune-empty -- --all
+  git clone file://$(pwd) newcopy
+  cd newcopy
+  git for-each-ref --format="delete %(refname)" refs/tags/ \
+      | grep -v refs/tags/my-module- \
+      | git update-ref --stdin
+  git gc --prune=now
+```
+
+Some might notice that the above filter-branch invocation will be really
+slow due to using --tree-filter; you could alternatively use the
+--index-filter option of filter-branch, changing the above commands to:
+
+```shell
+  git filter-branch \
+      --index-filter 'git ls-files \
+                          | grep -v ^src/ \
+                          | xargs git rm -q --cached;
+                      git ls-files -s \
+                          | sed "s%$(printf \\t)%&my-module/%" \
+                          | git update-index --index-info;
+                      git ls-files \
+                          | grep -v ^my-module/ \
+                          | xargs git rm -q --cached' \
+      --tag-name-filter 'echo "my-module-$(cat)"' \
+      --prune-empty -- --all
+  git clone file://$(pwd) newcopy
+  cd newcopy
+  git for-each-ref --format="delete %(refname)" refs/tags/ \
+      | grep -v refs/tags/my-module- \
+      | git update-ref --stdin
+  git gc --prune=now
+```
+
+However, for either filter-branch command there are a pile of caveats.
+First, some may be wondering why I list five commands here for
+filter-branch.  Despite the use of --all and --tag-name-filter, and
+filter-branch's manpage claiming that a clone is enough to get rid of
+old objects, the extra steps to delete the other tags and do another
+gc are still required to clean out the old objects and avoid mixing
+new and old history before pushing somewhere.  Other caveats:
+  * Commit messages are not rewritten; so if some of your commit
+    messages refer to prior commits by (abbreviated) sha1, after the
+    rewrite those messages will now refer to commits that are no longer
+    part of the history.  It would be better to rewrite those
+    (abbreviated) sha1 references to refer to the new commit ids.
+  * The --prune-empty flag sometimes misses commits that should be
+    pruned, and it will also prune commits that *started* empty rather
+    than just ended empty due to filtering.  For repositories that
+    intentionally use empty commits for versioning and publishing
+    related purposes, this can be detrimental.
+  * The commands above are OS-specific.  GNU vs. BSD issues for sed,
+    xargs, and other commands often trip up users; I think I failed to
+    get most folks to use --index-filter since the only example in the
+    filter-branch manpage that both uses it and shows how to move
+    everything into a subdirectory is linux-specific, and it is not
+    obvious to the reader that it has a portability issue since it
+    silently misbehaves rather than failing loudly.
+  * The --index-filter version of the filter-branch command may be two to
+    three times faster than the --tree-filter version, but both
+    filter-branch commands are going to be multiple orders of magnitude
+    slower than filter-repo.
+  * Both commands assume all filenames are composed entirely of ascii
+    characters (even special ascii characters such as tabs or double
+    quotes will wreak havoc and likely result in missing files or
+    misnamed files)
+
+## Solving this with fast-export/fast-import
+
+One can kind of hack this together with something like:
+
+```shell
+  git fast-export --no-data --reencode=yes --mark-tags --fake-missing-tagger \
+      --signed-tags=strip --tag-of-filtered-object=rewrite --all \
+      | grep -vP '^M [0-9]+ [0-9a-f]+ (?!src/)' \
+      | grep -vP '^D (?!src/)' \
+      | perl -pe 's%^(M [0-9]+ [0-9a-f]+ )(.*)$%\1my-module/\2%' \
+      | perl -pe 's%^(D )(.*)$%\1my-module/\2%' \
+      | perl -pe s%refs/tags/%refs/tags/my-module-% \
+      | git -c core.ignorecase=false fast-import --date-format=raw-permissive \
+            --force --quiet
+  git for-each-ref --format="delete %(refname)" refs/tags/ \
+      | grep -v refs/tags/my-module- \
+      | git update-ref --stdin
+  git reset --hard
+  git reflog expire --expire=now --all
+  git gc --prune=now
+```
+
+But this comes with some nasty caveats and limitations:
+  * The various greps and regex replacements operate on the entire
+    fast-export stream and thus might accidentally corrupt unintended
+    portions of it, such as commit messages.  If you needed to edit
+    file contents and thus dropped the --no-data flag, it could also
+    end up corrupting file contents.
+  * This command assumes all filenames in the repository are composed
+    entirely of ascii characters, and also exclude special characters
+    such as tabs or double quotes.  If such a special filename exists
+    within the old src/ directory, it will be pruned even though it
+    was intended to be kept.  (In slightly different repository
+    rewrites, this type of editing also risks corrupting filenames
+    with special characters by adding extra double quotes near the end
+    of the filename and in some leading directory name.)
+  * This command will leave behind huge numbers of useless empty
+    commits, and has no realistic way of pruning them.  (And if you
+    tried to combine this technique with another tool to prune the
+    empty commits, then you now have no way to distinguish between
+    commits which were made empty by the filtering that you want to
+    remove, and commits which were empty before the filtering process
+    and which you thus may want to keep.)
+  * Commit messages which reference other commits by hash will now
+    reference old commits that no longer exist.  Attempting to edit
+    the commit messages to update them is extraordinarily difficult to
+    add to this kind of direct rewrite.
+
+# Design rationale behind filter-repo
+
+None of the existing repository filtering tools did what I wanted;
+they all came up short for my needs. No tool provided any of the
+first eight traits below I wanted, and no tool provided more than
+two of the last four traits either:
+
+  1. [Starting report] Provide user an analysis of their repo to help
+     them get started on what to prune or rename, instead of expecting
+     them to guess or find other tools to figure it out.  (Triggered, e.g.
+     by running the first time with a special flag, such as --analyze.)
+
+  1. [Keep vs. remove] Instead of just providing a way for users to
+     easily remove selected paths, also provide flags for users to
+     only *keep* certain paths.  Sure, users could workaround this by
+     specifying to remove all paths other than the ones they want to
+     keep, but the need to specify all paths that *ever* existed in
+     **any** version of the repository could sometimes be quite
+     painful.  For filter-branch, using pipelines like `git ls-files |
+     grep -v ... | xargs -r git rm` might be a reasonable workaround
+     but can get unwieldy and isn't as straightforward for users; plus
+     those commands are often operating-system specific (can you spot
+     the GNUism in the snippet I provided?).
+
+  1. [Renaming] It should be easy to rename paths.  For example, in
+     addition to allowing one to treat some subdirectory as the root
+     of the repository, also provide options for users to make the
+     root of the repository just become a subdirectory.  And more
+     generally allow files and directories to be easily renamed.
+     Provide sanity checks if renaming causes multiple files to exist
+     at the same path.  (And add special handling so that if a commit
+     merely copied oldname->newname without modification, then
+     filtering oldname->newname doesn't trigger the sanity check and
+     die on that commit.)
+
+  1. [More intelligent safety] Writing copies of the original refs to
+     a special namespace within the repo does not provide a
+     user-friendly recovery mechanism.  Many would struggle to recover
+     using that.  Almost everyone I've ever seen do a repository
+     filtering operation has done so with a fresh clone, because
+     wiping out the clone in case of error is a vastly easier recovery
+     mechanism.  Strongly encourage that workflow by [detecting and
+     bailing if we're not in a fresh
+     clone](https://htmlpreview.github.io/?https://github.com/newren/git-filter-repo/blob/docs/html/git-filter-repo.html#FRESHCLONE),
+     unless the user overrides with --force.
+
+  1. [Auto shrink] Automatically remove old cruft and repack the
+     repository for the user after filtering (unless overridden); this
+     simplifies things for the user, helps avoid mixing old and new
+     history together, and avoids problems where the multi-step
+     process for shrinking the repo documented in the manpage doesn't
+     actually work in some cases.  (I'm looking at you,
+     filter-branch.)
+
+  1. [Clean separation] Avoid confusing users (and prevent accidental
+     re-pushing of old stuff) due to mixing old repo and rewritten
+     repo together.  (This is particularly a problem with filter-branch
+     when using the --tag-name-filter option, and sometimes also an
+     issue when only filtering a subset of branches.)
+
+  1. [Versatility] Provide the user the ability to extend the tool or
+     even write new tools that leverage existing capabilities, and
+     provide this extensibility in a way that (a) avoids the need to
+     fork separate processes (which would destroy performance), (b)
+     avoids making the user specify OS-dependent shell commands (which
+     would prevent users from sharing commands with each other), (c)
+     takes advantage of rich data structures (because hashes, dicts,
+     lists, and arrays are prohibitively difficult in shell) and (d)
+     provides reasonable string manipulation capabilities (which are
+     sorely lacking in shell).
+
+  1. [Old commit references] Provide a way for users to use old commit
+     IDs with the new repository (in particular via mapping from old to
+     new hashes with refs/replace/ references).
+
+  1. [Commit message consistency] If commit messages refer to other
+     commits by ID (e.g. "this reverts commit 01234567890abcdef", "In
+     commit 0013deadbeef9a..."), those commit messages should be
+     rewritten to refer to the new commit IDs.
+
+  1. [Become-empty pruning] Commits which become empty due to filtering
+     should be pruned.  If the parent of a commit is pruned, the first
+     non-pruned ancestor needs to become the new parent.  If no
+     non-pruned ancestor exists and the commit was not a merge, then it
+     becomes a new root commit.  If no non-pruned ancestor exists and
+     the commit was a merge, then the merge will have one less parent
+     (and thus make it likely to become a non-merge commit which would
+     itself be pruned if it had no file changes of its own).  One
+     special thing to note here is that we prune commits which become
+     empty, NOT commits which start empty.  Some projects intentionally
+     create empty commits for versioning or publishing reasons, and
+     these should not be removed.  (As a special case, commits which
+     started empty but whose parent was pruned away will also be
+     considered to have "become empty".)
+
+  1. [Become-degenerate pruning] Pruning of commits which become empty
+     can potentially cause topology changes, and there are lots of
+     special cases.  Normally, merge commits are not removed since they
+     are needed to preserve the graph topology, but the pruning of
+     parents and other ancestors can ultimately result in the loss of
+     one or more parents.  A simple case was already noted above: if a
+     merge commit loses enough parents to become a non-merge commit and
+     it has no file changes, then it too can be pruned.  Merge commits
+     can also have a topology that becomes degenerate: it could end up
+     with the merge_base serving as both parents (if all intervening
+     commits from the original repo were pruned), or it could end up
+     with one parent which is an ancestor of its other parent.  In such
+     cases, if the merge has no file changes of its own, then the merge
+     commit can also be pruned.  However, much as we do with empty
+     pruning we do not prune merge commits that started degenerate
+     (which indicates it may have been intentional, such as with --no-ff
+     merges) but only merge commits that become degenerate and have no
+     file changes of their own.
+
+  1. [Speed] Filtering should be reasonably fast
+
+# How do I contribute?
+
+See the [contributing guidelines](Documentation/Contributing.md).
+
+# Is there a Code of Conduct?
+
+Participants in the filter-repo community are expected to adhere to
+the same standards as for the git project, so the [git Code of
+Conduct](https://git.kernel.org/pub/scm/git/git.git/tree/CODE_OF_CONDUCT.md)
+applies.
+
+# Upstream Improvements
+
+Work on filter-repo and [its
+predecessor](https://public-inbox.org/git/[email protected]/)
+has also driven numerous improvements to fast-export and fast-import
+(and occasionally other commands) in core git, based on things
+filter-repo needs to do its work:
+
+  * git-2.48.0 (to be released Jan 2025)
+    * [fast-import: disallow more path components](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=da91a90c2f)
+    * [fast-import: disallow "." and ".." path components](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=4a2790a257)
+    * [fast-import: avoid making replace refs point to themselves](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=5e904f1a4a)
+  * git-2.28.0
+    * [fast-import: add new --date-format=raw-permissive format](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=d42a2fb72f)
+  * git-2.24.0
+    * [fast-export: handle nested tags](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=941790d7de)
+    * [t9350: add tests for tags of things other than a commit](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=8d7d33c1ce)
+    * [fast-export: allow user to request tags be marked with --mark-tags](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=a1638cfe12)
+    * [fast-export: add support for --import-marks-if-exists](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=208d69246e)
+    * [fast-import: add support for new 'alias' command](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=b8f50e5b60)
+    * [fast-import: allow tags to be identified by mark labels](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=f73b2aba05)
+    * [fast-import: fix handling of deleted tags](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=3164e6bd24)
+    * [fast-export: fix exporting a tag and nothing else](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=af2abd870b)
+    * [git-fast-import.txt: clarify that multiple merge commits are allowed](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=d1387d3895)
+  * git-2.23.0
+    * [t9350: fix encoding test to actually test reencoding](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=32615ce762)
+    * [fast-import: support 'encoding' commit header](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=3edfcc65fd)
+    * [fast-export: avoid stripping encoding header if we cannot reencode](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=ccbfc96dc4)
+    * [fast-export: differentiate between explicitly UTF-8 and implicitly
+      UTF-8](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=57a8be2cb0)
+    * [fast-export: do automatic reencoding of commit messages only if
+      requested](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=e80001f8fd)
+  * git-2.22.0
+    * [log,diff-tree: add --combined-all-paths option](
+        https://git.kernel.org/pub/scm/git/git.git/commit/?id=d76ce4f734)
+    * [t9300: demonstrate bug with get-mark and empty orphan commits](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=62edbec7de)
+    * [git-fast-import.txt: fix wording about where ls command can appear](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=a63c54a019)
+    * [fast-import: check most prominent commands first](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=5056bb7646)
+    * [fast-import: only allow cat-blob requests where it makes sense](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=7ffde293f2)
+    * [fast-import: fix erroneous handling of get-mark with empty orphan
+      commits](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=cf7b857a77)
+    * [Honor core.precomposeUnicode in more places](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=8e712ef6fc)
+  * git-2.21.0
+    * [fast-export: convert sha1 to oid](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=843b9e6d48)
+    * [git-fast-import.txt: fix documentation for --quiet option](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=f55c979b14)
+    * [git-fast-export.txt: clarify misleading documentation about rev-list
+      args](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=4532be7cba)
+    * [fast-export: use value from correct enum](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=b93b81e799)
+    * [fast-export: avoid dying when filtering by paths and old tags exist](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=1f30c904b3)
+    * [fast-export: move commit rewriting logic into a function for reuse](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=f129c4275c)
+    * [fast-export: when using paths, avoid corrupt stream with non-existent
+      mark](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=cd13762d8f)
+    * [fast-export: ensure we export requested refs](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=fdf31b6369)
+    * [fast-export: add --reference-excluded-parents option](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=530ca19c02)
+    * [fast-import: remove unmaintained duplicate documentation](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=25dd3e4889)
+    * [fast-export: add a --show-original-ids option to show
+      original names](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=a965bb3116)
+    * [git-show-ref.txt: fix order of flags](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=bd8d6f0def)
+  * git-2.20.0
+    * [update-ref: fix type of update_flags variable to
+      match its usage](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=e4c34855a2)
+    * [update-ref: allow --no-deref with --stdin](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=d345e9fbe7)
+  * git-1.7.3
+    * [fast-export: Fix dropping of files with --import-marks and path
+      limiting](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=4087a02e45)
+    * [fast-export: Add a --full-tree option](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=7f40ab0916)
+    * [fast-export: Fix output order of D/F changes](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=060df62422)
+    * [fast-import: Improve robustness when D->F changes provided in wrong
+      order](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=253fb5f889)
+  * git-1.6.4:
+    * [fast-export: Set revs.topo_order before calling setup_revisions](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=668f3aa776)
+    * [fast-export: Omit tags that tag trees](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=02c48cd69b)
+    * [fast-export: Make sure we show actual ref names instead of "(null)"](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=2374502c6c)
+    * [fast-export: Do parent rewriting to avoid dropping relevant commits](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=32164131db)
+    * [fast-export: Add a --tag-of-filtered-object option for newly
+      dangling tags](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=2d8ad46919)
+    * [Add new fast-export testcases](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=25e0ca5dd6)
+    * [fast-export: Document the fact that git-rev-list arguments are
+      accepted](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=8af15d282e)
+  * git-1.6.3:
+    * [git-filter-branch: avoid collisions with variables in eval'ed
+      commands](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=d5b0c97d13)
+    * [Correct missing SP characters in grammar comment at top of
+      fast-import.c](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=98e1a4186a)
+    * [fast-export: Avoid dropping files from commits](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=ebeec7dbc5)
+  * git-1.6.1.4:
+    * [fast-export: ensure we traverse commits in topological order](
+      https://git.kernel.org/pub/scm/git/git.git/commit/?id=784f8affe4)

.venv/Lib/site-packages/git_filter_repo-2.47.0.dist-info/RECORD

@@ -0,0 +1,13 @@
+../../Scripts/git-filter-repo.exe,sha256=Zhf2lAEdidPg1hjAz_Ejn8GhtY5zpa3ilnjx-c2ObQ4,108406
+__pycache__/git_filter_repo.cpython-312.pyc,,
+git_filter_repo-2.47.0.dist-info/COPYING,sha256=ZEeii_kaYaMWrMwlvI_NuMumZ7sibKtXEQfoEQ6i1BE,1159
+git_filter_repo-2.47.0.dist-info/COPYING.gpl,sha256=gXf5dRMhNSbfLPYYTY_5hsZ1r7UU1OaKQEAQUhuIBkM,18092
+git_filter_repo-2.47.0.dist-info/COPYING.mit,sha256=tzen05dpcjnBcX_Qb8c8I8MKce9gI2e16yQXu7G8Ci4,1054
+git_filter_repo-2.47.0.dist-info/INSTALLER,sha256=zuuue4knoyJ-UwPPXg8fezS7VCrXJQrAP7zeNuwvFQg,4
+git_filter_repo-2.47.0.dist-info/METADATA,sha256=gEdjLGg856P6DpBbvXrO9Mf-9OxHfDNEd2XCSOsnVEY,31010
+git_filter_repo-2.47.0.dist-info/RECORD,,
+git_filter_repo-2.47.0.dist-info/REQUESTED,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
+git_filter_repo-2.47.0.dist-info/WHEEL,sha256=PZUExdf71Ui_so67QXpySuHtCi3-J3wvF4ORK6k_S8U,91
+git_filter_repo-2.47.0.dist-info/entry_points.txt,sha256=BzaGaI1mp80VRtaSxXvI1tsJjxmVC5Wb9800OUNqRA4,57
+git_filter_repo-2.47.0.dist-info/top_level.txt,sha256=dr26pp94RCYQjpxw8uezW8EK1EP33r_Ed8EWPtxjKeM,16
+git_filter_repo.py,sha256=Z0R0E-Jz_HaAkokRF0iHC29gcvCLF-_pSGOpLYELfZQ,210911

.venv/Lib/site-packages/git_filter_repo-2.47.0.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (75.6.0)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

.venv/Lib/site-packages/git_filter_repo-2.47.0.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+git-filter-repo = git_filter_repo:main

.venv/Lib/site-packages/git_filter_repo-2.47.0.dist-info/top_level.txt

@@ -0,0 +1 @@
+git_filter_repo