[Tracker-discuss] [issue264] Mail gateway borks quotes and console sessions

anatoly techtonik added the comment: It seems that Roundup need a standards based reST or Markdown editor -- nosy: +techtonik ___ PSF Meta Tracker __

[Tracker-discuss] [issue407] bug in revision linking code

Ezio Melotti added the comment: URLs and issue numbers are converted by Roundup directly[0], all the other Python-specific linkifications are done in an extension[1]. The tests for the extension are in [3]. URLs are always converted to links, so the regexes in the extensions should figure o

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Martin v. Löwis added the comment: Ah, ok. I recall trying the format in a browser, and it (probably not surprisingly) failed. I guess it's then ok to support the format when adding repositories; I wouldn't change the schema, though (i.e. keep repo and branch separated).

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Éric Araujo added the comment: repo#branch is a supported format, not a convention for notation. For example, I always recommend using “hg clone http://hg.python.org/cpython#default” to avoid pulling 2.x branches. ___ PSF Meta Tracker

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Éric Araujo added the comment: How did it fail in a browser? It does not link to a fragment of the page, but the URI prior to the # sign still references a clonable Mercurial repo. About the schema: sure, no need to change it. Thanks for supporting repo#branch. _

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Éric Araujo added the comment: My GSoC student found the reason of the problem: When we put a full Mercurial URI like http://blah#branch, the patch generation fails, we have to go to the edit repo form (on another page) and fill in separately the base URI and the branch. It would be easier i

[Tracker-discuss] [issue264] Mail gateway borks quotes and console sessions

R David Murray added the comment: Even if it did, that would have zero effect on this issue. Personally, I'd rather deal with the occasional lost text when someone is doing an email reply than to deal with the reams of quoted text resulting from top post replies. I deal with the latter frequ

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Martin v. Löwis added the comment: I was hesitant to add another field into the UI, which is already overloaded, and it would make people assume that they have to fill out the branch field. I assumed that using named branches would be uncommon enough to let people who use them go through a sep

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Martin v. Löwis added the comment: This is now fixed in r88855 -- status: chatting -> resolved ___ PSF Meta Tracker ___ _

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Éric Araujo added the comment: Great, thanks! -- status: resolved -> chatting ___ PSF Meta Tracker ___ __

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Vinay Sajip added the comment: > Éric Araujo added the comment: > > My GSoC student found the reason of the problem: When we put a full > Mercurial >URI like http://blah#branch, the patch generation fails, we have to go to the >edit repo form (on another page) and fill in separately the

[Tracker-discuss] [issue405] Mercurial integration - "Create Patch" fails with "No such file or directory"

Éric Araujo added the comment: Yep, see subthread starting at http://mail.python.org/pipermail/python-dev/2011-March/109819.html ___ PSF Meta Tracker ___