git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC PATCH] Add "git show --follow-symlinks HEAD:symlink"

From
Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date
Apr 13, 2018, 19:33 UTC
Message-ID
<87h8oegavn.fsf@evledraar.gmail.com>
In-Reply-To
<20180413174819.GA19030@bod>
On Fri, Apr 13 2018, Michael Vogt wrote:
> The update patch is attached as an inline attachement.

Your patch still just shows up as a straight-up attachment in many E-Mail clients. Note the difference between what your patch (https://public-inbox.org/git/20180413174819.GA19030@bod/raw) and a patch that's not an attachment (https://public-inbox.org/git/0f0942043678fe76f8d654306482ee26fac643f0.1523617836.git.johannes.schindelin@gmx.de/raw) look like.

Try to "wget" both of those and apply them with "git am" on top of master, and note how what you're doing results in a broken patch.

This is why Documentation/SubmittingPatches suggests using format-patch & send-email. You don't *have* to use those tools, and can use something that's compatible with what's expected on-list, but what you're doing isn't that.

Previous: Michael VogtNext: Michael Vogt
Message 6 of 12 in “Add "git show --follow-symlinks HEAD:symlink"”
  1. Add "git show --follow-symlinks HEAD:symlink"Michael Vogt, Apr 9, 2018
  2. Ævar Arnfjörð BjarmasonApr 9, 2018
  3. Michael VogtApr 13, 2018
  4. Stefan BellerApr 13, 2018
  5. Michael VogtApr 13, 2018
  6. Ævar Arnfjörð BjarmasonApr 13, 2018
  7. support: git show --follow-symlinks HEAD:symlinkMichael Vogt, Apr 13, 2018
  8. Ævar Arnfjörð BjarmasonApr 13, 2018
  9. show: add --follow-symlinks option for <rev>:<path>Michael Vogt, Apr 16, 2018
  10. show: add --follow-symlinks option for <rev>:<path>Michael Vogt, Apr 16, 2018
  11. Junio C HamanoApr 16, 2018
  12. Michael VogtApr 13, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.