~dhruvin

Bangalore, India

https://dhruvin.dev

Free Software Developer

I develop and contribute to free, libre, and open-source software exclusively.

Trackers

~dhruvin/builds.sr.ht-guix

Last active 28 days ago

#194 Update the status of a patchset to superseded if newer version is submitted 6 days ago

Comment by ~dhruvin on ~sircmpwn/lists.sr.ht

Typo: The link has an additional trailing dot.

#194 Update the status of a patchset to superseded if newer version is submitted 6 days ago

Ticket created by ~dhruvin on ~sircmpwn/lists.sr.ht

Use-case:

  • As a contributor, I submit a patchset to a mailing-list
  • I am asked to revise the patchset
  • I submit an updated version of said patchset
  • With the proposed change: I see my old patchset's status changed from PROPOSED or NEEDS_REVISION to SUPERSEDED.

lists.sr.ht may also reply to the old patchset with content as below, to document the connection between said patchesets:

Superseded by: https://lists.sr.st/<~owner>/<list>/<message-id-of-latest-patch>

This is an alternative to implementing superseded use-case of https://todo.sr.ht/~sircmpwn/lists.sr.ht/193.

Parts of this have been discussed in public mumble meeting of January, 2022.

#193 Allow patchset authors to modify the status via email headers 6 days ago

Ticket created by ~dhruvin on ~sircmpwn/lists.sr.ht

Currently, only the mailing-list owners/moderators can update the status of submitted patchsets via email headers.

I propose allowing patchset authors to modify the status just like owners/maintainers do, but with allowed statuses limited to: SUPERSEDED, and (a new status) RETRACTED.

Use-case for superseded:

  • As a contributor, I submit a patchset to a project's mailing list
  • Upstream asks me to modify it on a different communication channel, e.g. IRC.
  • I submit next version of said patchset
  • With proposed change: I mark the previous version superseded via a reply to it with X-Sourcehut-Patchset-Update: SUPERSEDED email header

Use-case for retracted:

  • As a contributor, I submit a patchset to a mailing-list
  • Some time after the submission, but before the review from upstream, I find that the patchset has some undesired change, and I wish to not bother upstream about the patchset at all.
  • With proposed change: I mark the patchset retracted via a reply to it with X-Sourcehut-Patchset-Update: RETRACTED email header
  • Note: This can be also done via superseded status, but it requires submission of the newer version of patchset first.

This will lessen the burden of maintaining status of submitted patches on owners/moderators. Something which I find is common for active projects with a lot of external contributions.

Parts of this have been discussed in public mumble meeting of January, 2022.

#3 Lint guixrus packages only 11 days ago

Comment by ~dhruvin on ~whereiseveryone/guixrus

656d14f broke guix pull. Find a different way of running the code.

RESOLVED FIXED REPORTED

#10 Document how to use todo 13 days ago

~dhruvin assigned ~dhruvin to #10 on ~whereiseveryone/guixrus

#10 Document how to use todo 13 days ago

docs added by ~dhruvin on ~whereiseveryone/guixrus

#10 Document how to use todo 13 days ago

Ticket created by ~dhruvin on ~whereiseveryone/guixrus

#1 Update sc-im to v0.8.2 13 days ago

packages added by ~dhruvin on ~whereiseveryone/guixrus

#8 Add gomuks 13 days ago

packages added by ~dhruvin on ~whereiseveryone/guixrus

#7 Add git-interactive-rebase-tool 13 days ago

packages added by ~dhruvin on ~whereiseveryone/guixrus