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.
The documentation for in-directory reads:
"Return a sequence that produces all of the paths for files, directories, and
links with dir. If dir is not #f, then every produced path starts with dir as
its prefix. If dir is #f, then paths in and relative to the current directory
are produced."
Was
On Monday, Matthias Felleisen wrote:
>
> I think Jay is expressing an Eli-concern: we need to distribute the
> full source to determine whether something can be thrown away.
It's more than just the dependencies between libraries -- it's the
fact that expanding the code (before "stripping", but se
6 matches
Mail list logo
