gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2021-04-08	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2020-05-13	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2020-02-01	Add latest changes from gitlab-org/gitlab@master	GitLab Bot

2019-12-16	Add latest changes from gitlab-org/gitlab@masterogolowinski-master-patch-80898	GitLab Bot

2017-07-11	Support multiple Redis instances based on queue type	Paul Charlton

2017-02-20	Use newer mail_room to get `require_relative` support	Gabriel Mazetto

2016-11-16	Make mail_room idle_timeout option configurable.	Marin Jankovski

2016-10-26	Updated mail_room and added sentinel support to Reply by Email	Gabriel Mazetto

2016-10-24	Fix reply-by-email not working due to queue name mismatch	Stan Hu
	mail_room was configured to deliver mail to the `incoming_email` queue while `EmailReceiveWorker` was reading the `email_receiver` queue. Adds a migration that repeats the work of a previous migration to ensure all mails that wound up in the old queue get processed. Closes #23689
2016-08-04	Synced mail_room.yml with the one in omnibus	Gabriel Mazetto
	Added a comment to remember developers to open merge request to omnibus in future changes of the file.
2016-08-04	Fixed specs for Gitlab::Redis and code for Redis Sentinel support	Gabriel Mazetto

2016-08-04	Deduplicated resque.yml loading from several places	Gabriel Mazetto
	We will trust redis configuration params loading to Gitlab::RedisConfig.
2016-06-10	Don't require Gitlab::Redis in mail_room.yml if it's already defined	Rémy Coutable
	Signed-off-by: Rémy Coutable <remy@rymai.me>
2016-04-04	Add Gitlab::Redis connection pool	Jacob Vosmaer

2016-03-25	Improve and finish the fallback to the In-Reply-To and References header for ↵	Rémy Coutable
	the reply-by-email feature A few things to note: - The IncomingEmail feature is now enabled even without a correctly-formatted sub-address - Message-ID for new thread mail are kept the same so that subsequent notifications to this thread are grouped in the thread by the email service that receives the notification (i.e. In-Reply-To of the answer == Message-ID of the first thread message) - To maximize our chance to be able to retrieve the reply key, we look for it in the In-Reply-To header and the References header - The pattern for the fallback reply message id is "reply-[key]@[gitlab_host]" - Improve docs thanks to Axil
2016-03-09	Parse config/resque.yml in one place only	Jacob Vosmaer

2016-02-27	Don't load all of GitLab in mail_room	Douwe Maan
	Fixes #12731
2015-10-13	Make Reply by email easier to configure	Douwe Maan