18 Jun, 2014

1 commit


10 Jun, 2014

2 commits

  • * 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.
    Pierre de La Morinerie
     

05 May, 2014

1 commit


19 Feb, 2014

4 commits

  • 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
     
  • For instance, the email "Subject" field changes from:
    
        Mattt / Ground Control | Saving issue doesn't work sometimes (#1234)
    
    to:
    
        Ground Control | Saving issue doesn't work sometimes (#1234)
    
    Rationale:
    
    * Most people are receiving email notifications about a single fork:
    the project activity, issues and merge requests are happening either
    in a root repository or in a fork, but less often in several forks.
    
    * It removes noise from the email subject. The namespace of the project
    can still be read in the email body.
    
    * For Entreprise users that have a single namespace "MyEntreprise",
    having this repeated in every email subject is very noisy.
    Pierre de La Morinerie
     
  • This changes email subjects from:
    
        GitLab | Team / Project | Note for issue #1234
    
    to:
    
        Team / Project | Note for issue #1234
    
    Rationale:
    
    * Emails should be as meaningful as possible, and emphasize content over
    chrome. The "GitLab" name is more chrome than content.
    
    * Users can tell an email coming from GitLab by the sender or the header
    in the email content.
    
    * An organization that works mainly with GitLab knows that
    every SVC email comes from GitLab. For these organizations, having
    "GitLab" in front of every email is just noise hiding the meaningful
    information.
    Pierre de La Morinerie
     
  • Pierre de La Morinerie
     

24 Jan, 2014

1 commit


09 Dec, 2013

1 commit


11 Sep, 2013

1 commit


17 Jul, 2013

1 commit


19 Mar, 2013

1 commit


01 Feb, 2013

2 commits


15 Jan, 2013

2 commits


09 Jan, 2013

2 commits


02 Jan, 2013

1 commit


31 Dec, 2012

2 commits


30 Dec, 2012

1 commit


28 Dec, 2012

1 commit


20 Dec, 2012

3 commits


29 Nov, 2012

1 commit


18 Oct, 2012

1 commit


13 Oct, 2012

1 commit


06 Sep, 2012

1 commit


29 Aug, 2012

1 commit


27 Aug, 2012

1 commit


20 Aug, 2012

2 commits


10 Aug, 2012

1 commit


09 Aug, 2012

1 commit


06 Aug, 2012

2 commits


19 Jul, 2012

1 commit