https://bugzilla.redhat.com/show_bug.cgi?id=1508384

            Bug ID: 1508384
           Summary: Review Request: git-publish - Prepare and store patch
                    revisions as git tags
           Product: Fedora
           Version: rawhide
         Component: Package Review
          Severity: medium
          Priority: medium
          Assignee: nob...@fedoraproject.org
          Reporter: stefa...@redhat.com
        QA Contact: extras...@fedoraproject.org
                CC: package-review@lists.fedoraproject.org



Spec URL: https://github.com/stefanha/git-publish/blob/master/git-publish.spec
SRPM URL:
https://kojipkgs.fedoraproject.org/work/tasks/345/22840345/git-publish-1.3-1.fc26.src.rpm

Description:
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.

Fedora Account System Username: stefanha

This is my first Fedora package and I have asked rjones to be my sponsor.  I am
the upstream maintainer for git-publish and also maintain a git-publish Copr
repo here: https://copr.fedorainfracloud.org/coprs/stefanha/git-publish/.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
_______________________________________________
package-review mailing list -- package-review@lists.fedoraproject.org
To unsubscribe send an email to package-review-le...@lists.fedoraproject.org

Reply via email to