[SciPy-Dev] issues trac migration review
Tue Apr 23 12:05:14 CDT 2013
On Tue, Apr 23, 2013 at 12:56 PM, Skipper Seabold <firstname.lastname@example.org> wrote:
> On Mon, Apr 22, 2013 at 7:12 PM, <email@example.com> wrote:
>> On Mon, Apr 22, 2013 at 4:34 PM, <firstname.lastname@example.org> wrote:
>>> On Mon, Apr 22, 2013 at 3:48 PM, Skipper Seabold <email@example.com> wrote:
>>>> On Mon, Apr 22, 2013 at 3:27 PM, <firstname.lastname@example.org> wrote:
>>>>> Is there a way to get changeset links ?
>>>>> for example
>>>>> in last comment here https://github.com/jseabold/scipy-trac-migration/issues/620
>>>> Yeah, that should be doable. I'll add it to the list.
>>> same for tickets
>>> 3rd comment here https://github.com/jseabold/scipy-trac-migration/issues/1081
>> looks like there are quite a few ways of specifying changesets/revision
>> in last comment here https://github.com/jseabold/scipy-trac-migration/issues/992
> I'm only grabbing the ones that are specified changeset:XXXX and rXXX.
> Y'all are more familiar with trac. Is this sufficient? Do people use
> the [XXX] traclinks?
> Are there any other traclinks that I should look out for? It doesn't
> look like there is much use of ticket:XXXX but rather #XXX. There are
> some cross links to numpy tickets that I can probably update to
> numpy's github issue tracker, but I'd prefer to do this only if you
> think it's worth it. Let me know.
I think I used only these 4
changeset:XXXX and rXXX
ticket:XXXX and #XXX
none of the other ones look very familiar
> SciPy-Dev mailing list
More information about the SciPy-Dev