<!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="">

<blockquote dir="auto">

<p>IMO we don't need <code>glimport</code> at all, we can also document the little set of commands executed by <code>make glimport</code>. But then I didn't want to be too intrusive. Maybe someone is used to use glimport - why break it without need ?</p>

</blockquote>

<p dir="auto">I think the target group for the functionality at hand is the ones who update gnulib and that's me and you in this project for the last 3 years. Having it there as a documented shortcut to switching the gnulib to the latest upstream makes sense, but keeping it for compatibility seems unnecessary to me.</p>

</div>

</div>

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

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

—

<br>

Reply to this email directly or <a href="https://gitlab.com/gnutls/gnutls/merge_requests/900#note_136349699">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/5b8f123d11e9075134497dcbbb25b3a3/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/900#note_136349699"}}</script>

</p>

</div>

</body>

</html>