Upstream software project

stgit

manage stacks of patches in a git repository

About stgit

manage stacks of patches in a git repository

This project links 4 native package records across 2 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

Debian 12 (Bookworm): 2 package records; Debian 13 (Trixie): 2 package records. Catalog coverage diagram, not an application screenshot.stgit: recorded package coverageDebian 12 (Bookworm)2 recordsDebian 13 (Trixie)2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
stgit
Publisher
Not authoritatively mapped
Native package records
4
Operating systems
debian-12, debian-13
License expression
Not reported
Source repository
Not reported

Source-reported description

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

set of contributed script to help working with stgit

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 stgit

    bookworm (Debian 12 (Bookworm)) (vcs): manage stacks of patches in a git repository

    0.19-1.1: all

  2. Package stgit-contrib

    bookworm (Debian 12 (Bookworm)) (vcs): set of contributed script to help working with stgit

    0.19-1.1: all

    Source: stgit

Debian 13 (Trixie)

  1. Package stgit

    trixie (Debian 13 (Trixie)) (vcs): manage stacks of patches in a git repository

    0.19-2: all

  2. Package stgit-contrib

    trixie (Debian 13 (Trixie)) (vcs): set of contributed script to help working with stgit

    0.19-2: all

    Source: stgit

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.