From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: patch links do not have stable checksums
Date: Sat, 18 Feb 2017 22:50:27 +0100 [thread overview]
Message-ID: <CAHmME9pkV=DAdk9zMhuxQugZyEgPnR69qx=8foRERA=AEoaQaw@mail.gmail.com> (raw)
In-Reply-To: <20170218173219.GC1577@john.keeping.me.uk>
Seems most reasonable to simply keep it something static and not add a nob.
However, John - you raise a good point. Git's diff feature isn't
exactly stable itself, with all sorts of interesting new diffing
strategies being tried out in newer versions. So perhaps this isn't
really an feasible goal in the first place...
prev parent reply other threads:[~2017-02-18 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 8:45 ilovezfs
2017-02-18 17:32 ` john
2017-02-18 21:50 ` Jason [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHmME9pkV=DAdk9zMhuxQugZyEgPnR69qx=8foRERA=AEoaQaw@mail.gmail.com' \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).