git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "jonsmirl@gmail.com" <jonsmirl@gmail.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Making file permissions match
Date: Wed, 3 Aug 2016 10:14:33 -0400	[thread overview]
Message-ID: <CAKON4OzzKWXXbnTW+NEhSNs9WPWq=AS970YeLMRx95ObYhGaxA@mail.gmail.com> (raw)
In-Reply-To: <20160803140730.GA2390@atze2.lan>

On Wed, Aug 3, 2016 at 10:07 AM, Torsten Bögershausen <tboegi@web.de> wrote:
> On Wed, Aug 03, 2016 at 09:46:06AM -0400, jonsmirl@gmail.com wrote:
>> I'm working with some Windows programmers that don't believe in file
>> permissions They keep sending me zip files of their source tree.  I
>> have my copy of the tree in git on Linux with all of the correct file
>> permissions.
>>
>> So I unzip the archive they send me and to see what they changed. I
>> unzip it on top of my git tree. But now all of the file permissions
>> don't match. The code deltas are there but there is also all of this
>> noise from the file permissions.
>>
>> Is there an easy way to deal with this? I want to keep the code deltas
>> and ignore the permission changes. Since there are about 100K files
>> this is too much to do manually.
>
> (I'm not sure if I understand "match" correctly)
>
> You can ignore changes in the executable permissions:
> git config core.filemode false
>
> Please let us know if it works

Thanks, that might work. It will take a few hours to check since the
repo is huge.

-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2016-08-03 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-03 13:46 Making file permissions match jonsmirl
2016-08-03 14:07 ` Torsten Bögershausen
2016-08-03 14:14   ` jonsmirl [this message]
2016-08-03 14:21 ` Johannes Schindelin

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKON4OzzKWXXbnTW+NEhSNs9WPWq=AS970YeLMRx95ObYhGaxA@mail.gmail.com' \
    --to=jonsmirl@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=tboegi@web.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).