- 17 11月, 2015 2 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 20 8月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 19 8月, 2015 1 次提交
-
-
由 Douwe Maan 提交于
-
- 15 2月, 2015 1 次提交
-
-
由 Vinnie Okada 提交于
Make the following changes to deal with new behavior in Rails 4.1.2: * Use nested resources to avoid slashes in arguments to path helpers.
-
- 03 7月, 2014 1 次提交
-
-
由 Pierre de La Morinerie 提交于
* send a 'In-Reply-To' header along the 'References' header * subject of answers to an existing thread begins with 'Re: '
-
- 18 6月, 2014 1 次提交
-
-
由 Jacob Vosmaer 提交于
This reverts commit 97fd990e, reversing changes made to f451a697. Conflicts: app/mailers/emails/notes.rb app/mailers/emails/projects.rb
-
- 10 6月, 2014 2 次提交
-
-
由 Pierre de La Morinerie 提交于
* send a ‘In-Reply-To’ header along the ‘References’ header * subject of answers to an existing thread begins with ‘Re: ’ This fixes threading with at least Mail.app and Airmail.
-
由 Pierre de La Morinerie 提交于
This fixes email threading in Mail.app, that doesn't like when a thread doesn't have stable recipients. For instance, here is a possible sender-recipient combinations before: From: A To: Me New issue From: B To: Me Reply on new issue From: A To: Me Another reply Mail.app doesn't see B as a participant to the original email thread, and decides to break the thread: it will group all messages from A together, and separately all messages from B. This commit makes the thread look like this: From: A To: gitlab/project Cc: Me New issue From: B To: gitlab/project Cc: Me Reply on new issue From: A To: gitlab/project Cc: Me Another reply Mail.app sees a common recipient, and group the thread correctly.
-
- 06 5月, 2014 1 次提交
-
-
由 Philip Blatter 提交于
Added email threading for update emails on issues and merge requests (if the mail client support the References: mail header)
-
- 03 3月, 2014 1 次提交
-
-
由 Pierre de La Morinerie 提交于
When an email notification concerns a specific object (issue, note, merge request, etc.), add a link to the footer of the email that opens the item's page in a web browser. Rationale: * The link is predictable: always the same text, always at the same location, like any reliable tool. * It allows to remove the inline-title in many emails, and leave only the actual content of the message.
-
- 20 2月, 2014 2 次提交
-
-
由 Pierre de La Morinerie 提交于
This changes the email "From" field from "gitlab@example.com" to either: * "John Doe <gitlab@example.com>" if the author of the action is known, * "GitLab <gitlab@example.com>" otherwise. Rationale: this allow mails to appear as if they were sent by the author. It appears in the mailbox more like a real discussion between the sender and the receiver ("John sent: we should refactor this") and less like a robot notifying about something.
-
由 Pierre de La Morinerie 提交于
This changes the email subjects for issues and merge request notifications from: Team / Project | Note for issue #1234 to: Team / Project | Saving issue doesn't work sometimes (#1234) Rationale: * Scan the subject of the email notification more easily when catching up with a lot of notifications. Instead of having to open the email to get the title of the issue or merge request, one can simply read the subject of the email. * Group messages by subject: email clients will group emails in threads if they have the same subject.
-
- 20 1月, 2014 1 次提交
-
-
由 skv 提交于
-
- 09 11月, 2013 1 次提交
-
-
由 Drew Blessing 提交于
There was some funny syntax in merge request email templates. There was a ! before the merge request number when there probably should be a #. This may be some carry over from markdown but should not be in email templates. There were also some capitalization discrepancies among the subject lines. For those OCD people out there I standardized the capitalization. :)
-
- 22 8月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 02 7月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
- 28 3月, 2013 3 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
-
由 Dmitriy Zaporozhets 提交于
-
- 20 3月, 2013 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
-