#1215: Factor out Duplicated Code in vivify/fetch opcodes
-----------------------+----------------------------------------------------
Reporter: chromatic | Owner: soh_cah_toa
Type: cage | Status: assigned
Priority: minor | Milestone:
Component: core | Version: 1.7.0
Severity: low | Keywords: ops newbie
Lang: | Patch:
Platform: all |
-----------------------+----------------------------------------------------
Comment(by jkeenan):
Replying to [comment:6 cotto]:
> It sounds like pull requests vs. patches is a point that could use some
discussion.
cotto,
I strongly disagree with the direction you're heading in.
If a Parrot contributor is working on a problem covered by a Trac ticket,
then it is reasonable to expect that the solution developed for that
problem will appear '''in the ticket'''.
If people also want to issue git pull requests, that's fine. And if it's
a problem not being tracked by a Trac ticket -- say, a problem small
enough to be pasted -- then that's fine as well.
But if we've opened a ticket, and if a developer has taken the ticket,
then the proposed solution should be attached to the ticket.
Thank you very much.
kid51
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1215#comment:7>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
