I don't know if it is worth going this route, but SirMail can pull out
attachments already, so the libraries are there.
Robby
On Mon, Mar 19, 2012 at 12:41 AM, Eli Barzilay wrote:
> Three hours ago, Sam Tobin-Hochstadt wrote:
>> On Sat, Mar 17, 2012 at 10:55 AM, Eli Barzilay wrote:
>> > The rea
Three hours ago, Sam Tobin-Hochstadt wrote:
> On Sat, Mar 17, 2012 at 10:55 AM, Eli Barzilay wrote:
> > The real issue is whether it's really alright with you...
> > Currently, something that I do and I'm sure others do it to, is
> > keep the bug in my mailbox with any followup discussions. In so
On Sat, Mar 17, 2012 at 10:55 AM, Eli Barzilay wrote:
> The real issue is whether it's really alright with you... Currently,
> something that I do and I'm sure others do it to, is keep the bug in my
> mailbox with any followup discussions. In some cases the followups contain
> enough information
On Mar 17, 2012, at 7:55 AM, Eli Barzilay wrote:
> The real issue is whether it's really alright with you... Currently,
> something that I do and I'm sure others do it to, is keep the bug in my
> mailbox with any followup discussions. In some cases the followups contain
> enough information
The real issue is whether it's really alright with you... Currently,
something that I do and I'm sure others do it to, is keep the bug in my
mailbox with any followup discussions. In some cases the followups contain
enough information so I'll keep only that and not the original. With the
github
To clarify, we gain the ability to use markdown. (though it will probably
take some time to get used to it, due to the racket use of backquotes, and
we lose the ability to use attachments. If github add an attachment
facility we will probably get it via the web interface only unless the also
parse
No, these bugs will be posted through the same script that is running on the
server now. This is also needed so that previous DrRacket versions will be
able to post bugs.
On Mar 17, 2012, at 9:48 AM, Philippe Meunier wrote:
> Sam Tobin-Hochstadt wrote:
>> 1. You'll be able to enter a GitHub
Sam Tobin-Hochstadt wrote:
>1. You'll be able to enter a GitHub username and password in DrRacket to
> post bugs as your GitHub user. For people who don't do this (mostly
> for people who don't have a GitHub account), the bug will be
> submitted using a GitHub account that is specifically se
On Fri, Mar 16, 2012 at 7:19 PM, John Clements
wrote:
> On Mar 16, 2012, at 3:56 PM, Sam Tobin-Hochstadt wrote:
>
> * The bug notification-turned-mailing-list interaction aspect of Gnats
> is mostly lost. GitHub sends out notifications when a bug is
> created, but it will *not* send out fu
For what it's worth, github-flavored markdown (used in issues and
pull requests) does let you embed inline images and
syntax-highlighted source code, written like this:
scheme
(lambda (foo)
;; scheme source here
...)
You can see an example in t
On Mar 16, 2012, at 3:56 PM, Sam Tobin-Hochstadt wrote:
> * The bug notification-turned-mailing-list interaction aspect of Gnats
>is mostly lost. GitHub sends out notifications when a bug is
>created, but it will *not* send out further comments unless you're
>participating in the di
Summary: I'm preparing to switch the Racket bug database to GitHub.
At the end of this email, there's a long list of reasons why (and a
few limitations).
Action: Please visit http://samth2.ccs.neu.edu:8080/github-auth/ to make
it possible to associate your existing bugs with your GitHub account.
12 matches
Mail list logo
