ahcm apply blah.txt foo.txt /prj/foo
- Copy all files under directory mypatch over corresponding files in
/prj/foo. Do the same for blah.txt and foo.txt
If file doesn't exist under target dir, it's NOT created.
Also other simple but handy "dirty" CM operations are supported for those unmanaged situations. ;-)
1 maintainer
Metadata
1 maintainer
Release files for ahcm 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ahcm-0.1.zip | 15.6 kB | Without provenance | Details for ahcm-0.1.zip |
Release files / ahcm-0.1.zip
| Download URL | ahcm-0.1.zip |
|---|---|
| Size | 15.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
446a91f400d24fe9366fac3216160bc836769dbd75b6314fe6c98a299180deb7
|
|
BLAKE2b-256 checksum How to use checksums |
293452eaa07e9574788000260af0211a00ea347b32a6fcbe9b29983894ac8dc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ahcm 0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
