<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">

<html lang="en">

<head>

<meta content="text/html; charset=utf-8" http-equiv="Content-Type">

<title>

GitLab

</title>

<style>img {

max-width: 100%; height: auto;

}

</style>

</head>

<body>

<div class="content">

<div style="">

<p dir="auto">I think adding the upstream as remote is the less error prone; on personal forks there is not much incentive to keep an up-to-date master so we may not be able to rely on it being recent or even existing at all. <a href="https://gitlab.com/rockdaboot" data-user="267665" data-reference-type="user" data-container="body" data-placement="bottom" class="gfm gfm-project_member" title="Tim Rühsen">@rockdaboot</a> what do you think?</p>

</div>

</div>

<div class="footer" style="margin-top: 10px;">

<p style="font-size: small; color: #777;">

—

<br>

Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/merge_requests/964#note_155922192">view it on GitLab</a>.

<br>

You're receiving this email because of your account on gitlab.com.

If you'd like to receive fewer emails, you can

<a href="https://gitlab.com/sent_notifications/91cfbbf122a43da998339587fb459457/unsubscribe">unsubscribe</a>

from this thread or

adjust your notification settings.

<script type="application/ld+json">{"@context":"http://schema.org","@type":"EmailMessage","action":{"@type":"ViewAction","name":"View Merge request","url":"https://gitlab.com/gnutls/gnutls/merge_requests/964#note_155922192"}}</script>

</p>

</div>

</body>

</html>