[SciPy-Dev] issues trac migration review
Thu Apr 25 19:25:43 CDT 2013
On Thu, Apr 25, 2013 at 8:22 PM, <firstname.lastname@example.org> wrote:
> On Thu, Apr 25, 2013 at 8:10 PM, Skipper Seabold <email@example.com> wrote:
>> On Thu, Apr 25, 2013 at 7:49 PM, <firstname.lastname@example.org> wrote:
>>> incorrect crosslinks again
>>> comments like this are pretty annoying since the create backlinks
>>> a collection of backlinks
>>> trac didn't have the backlinks, so incorrect links were less of a distraction.
>>> Is there anything we can do? or maybe it's not worth it with old tickets.
>> Ugh, I spent an hour fixing the regex for this last night and it
>> happens automatically on github anyway.
>> I just put that in a code block and it goes away, but no there's no
>> way to really do that programmatically.
> Yes, I realized that before, there is no way to recognize this with a regex.
Well it doesn't convert it to gh-. That's the regex I control.
> I was thinking more about whether we should manually edit the
> offending comments.
Sounds fine to me.
> At least I would prefer, when I see a wrong backlink in one of the
> issues that I look at, to just go and edit the linking comment.
> It would trigger a notification, I assume.
I don't think a manual edit would. Doing it with the code deletes the
old comments and pushes new ones, so that would.
I think we're out of the notification doghouse now though (at least
More information about the SciPy-Dev