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

Re: Filtering mode changes

From
SBSanti Béjar <sbejar@gmail.com>
Date
Aug 1, 2008, 12:32 UTC
Message-ID
<8aa486160808010532k3932979er1a457b0d627e988@mail.gmail.com>
In-Reply-To
<loom.20080801T111754-982@post.gmane.org>
On Fri, Aug 1, 2008 at 13:25, Stefan Naewe <stefan.naewe+git@gmail.com> wrote:
Show 8 quoted lines
> Hi there.
>
> Here's my story:
>
> - I did some minor modifications to a repo that I want to 'give back'.
> - I worked on my own branch (of course).
> - I was stupid to edit the files (that live on a linux box) through a windows
>  network share.
Then, you should set core.fileMode to false.
> - When I created diffs (using 'git format-patch') to send send 'upstream', I
>  noticed that the edited files got their executable bit set (old mode 100644 ->
>  new mode 100755)
You can just edit the patches and remove the "old/new mode" lines.
> - I created another commit to undo the mode changes.

You can use "git rebase -i" and edit (or squash) the revision before generating the patch.

Santi
Previous: Matt Pearson
Message 3 of 3 in “Filtering mode changes”
  1. Stefan NaeweAug 1, 2008
  2. Matt PearsonAug 1, 2008
  3. Santi BéjarAug 1, 2008

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.