[SciPy-Dev] issues trac migration review
Tue Apr 23 12:06:11 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>
> >>> On Mon, Apr 22, 2013 at 3:27 PM, <firstname.lastname@example.org> wrote:
> >>>> Is there a way to get changeset links ?
> >>>> for example
> >>>> changeset:5972
> >>>> in last comment here
> >>> Yeah, that should be doable. I'll add it to the list.
> >> Thanks,
> >> same for tickets
> >> ticket:1082
> >> 3rd comment here
> > looks like there are quite a few ways of specifying changesets/revision
> > r6160
> > in last comment here
> 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.
There is commit:<sha-1> which links to the commit on github. See, for
> SciPy-Dev mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SciPy-Dev