this idea as
Tracking divergence from upstream as a bug in the Subject field.
--
\When you go in for a job interview, I think a good thing to |
`\ ask is if they ever press charges. -- Jack Handey |
_o__) |
Ben
Joey Hess [EMAIL PROTECTED] writes:
Hmm, another thought is, I sometimes have a changelog like this:
* New upstream release.
- Including my fix for foo.
- And a better approach than my old hack to fix bar.
It would be nice to be able to add bug numbers to close the
divergences when
Joey Hess [EMAIL PROTECTED] writes:
I think that going back and collecting all the patches I've sent to
upstreams over the years, and any I've dropped on the floor, and
keeping it up-to-date going forward will help me maintain my
packages better anyway, so I plan to do that this week. Though
Ben Finney wrote:
Care to discuss what tags you plan to use, so an attempt at consensus
can be made on naming the tags for this purpose?
I'm using a divergence usertag, with users [EMAIL PROTECTED] and
[EMAIL PROTECTED] (so it'll show up on my bugs page, and the
package's bug page -- not
4 matches
Mail list logo
