Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Move mailing list archives to Google Groups #3671

Closed
bstrie opened this issue Oct 6, 2012 · 1 comment
Closed

Move mailing list archives to Google Groups #3671

bstrie opened this issue Oct 6, 2012 · 1 comment
Labels
C-enhancement Category: An issue proposing an enhancement or a PR with one.

Comments

@bstrie
Copy link
Contributor

bstrie commented Oct 6, 2012

Google Groups makes it nicer to browse archived threads compared to what Pipermail currently offers. The dev-servo mailing list already does this (note the archive link at https://lists.mozilla.org/listinfo/dev-servo ). I hear that a lot of other Mozilla mailing lists do this as well.
@bstrie
Copy link
Contributor Author

bstrie commented Dec 11, 2012

I've recently discovered that rust-dev is mirrored to Gmane:

http://thread.gmane.org/gmane.comp.lang.rust.devel/

...which doesn't provide the commenting facilities of Google Groups, but at least now browsing and searching is possible. Closing this.

@bstrie bstrie closed this as completed Dec 11, 2012
bors pushed a commit to rust-lang-ci/rust that referenced this issue May 15, 2021
@topecongiro
Do not consider macro-origin await as chain item (rust-lang#3671)
3200af9
RalfJung pushed a commit to RalfJung/rust that referenced this issue Jun 15, 2024
@bors
Auto merge of rust-lang#3671 - tiif:epoll_create1_minor_fix, r=RalfJung
ccb5f52 
Minor fix: Change wording of epoll_create1 and socketpair's throw_unsup_format

This PR slightly changes the wording and format of ``epoll_create1``'s ``throw_unsup_format`` to match other shims. It is just a minor detail that I couldn't help but want to change while reading it. Sorry if it is not appropriate to open a PR for such minor detail.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-enhancement Category: An issue proposing an enhancement or a PR with one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bstrie