Upstream software project

git-publish

Prepare and store patch revisions as git tags

About git-publish

Prepare and store patch revisions as git tags

This project links 4 native package records across 4 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

git-publish repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.git-publish: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
git-publish
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
debian-12, debian-13, fedora-43, fedora-44
License expression
MIT
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

git-publish handles repetitive and time-consuming details of managing patch email submission. It works with individual patches as well as patch series and has support for pull request emails. Each revision is stored as a git tag including the cover letter (if any). This makes it easy to refer back to previous revisions of a patch. Numbering is handled automatically and the To:/Cc: email addresses are remembered across revisions to save you retyping them. Many projects have conventions for submitting patches. It is possible to encode them as a .gitpublish file and hooks/ scripts. This automatically uses the right settings and can run a coding style checker or linting tools before emails are sent.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. Package git-publish

    bookworm (Debian 12 (Bookworm)) (vcs): git command to prepare and store patch revisions as git tags

    1.8.1-1: all

Debian 13 (Trixie)

  1. Package git-publish

    trixie (Debian 13 (Trixie)) (vcs): git command to prepare and store patch revisions as git tags

    1.8.1-1: all

Fedora 43

  1. Package git-publish

    43 (Fedora 43) (Unspecified): Prepare and store patch revisions as git tags

    1.8.2-4.fc43: noarch

    Source: git-publish

Fedora 44

  1. Package git-publish

    44 (Fedora 44) (Unspecified): Prepare and store patch revisions as git tags

    1.8.2-5.fc44: noarch

    Source: git-publish

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.