From: Avery Pennarun <apenwarr@gmail.com>
To: Chris Packham <judge.packham@gmail.com>
Cc: "Łukasz Stelmach" <lukasz.stelmach@iem.pw.edu.pl>, git@vger.kernel.org
Subject: Re: merging unmanaged working tree
Date: Mon, 15 Mar 2010 15:01:55 -0500 [thread overview]
Message-ID: <32541b131003151301i69e5df1doc463406738086a89@mail.gmail.com> (raw)
In-Reply-To: <a038bef51003151258q2a4ba7dfwe84b29854c03d7eb@mail.gmail.com>
2010/3/15 Chris Packham <judge.packham@gmail.com>:
> The downside with this is that it is very likely that your files will
> pick up an executable bit from the file system on your pen drive which
> will need to be fixed up before you commit them.
If you have this problem, you might want to look at the core.fileMode
option. (See 'man git-config').
Have fun,
Avery
next prev parent reply other threads:[~2010-03-15 20:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 11:34 merging unmanaged working tree Łukasz Stelmach
2010-03-15 12:34 ` Daniel
2010-03-15 15:19 ` Łukasz Stelmach
2010-03-15 19:22 ` Avery Pennarun
2010-03-15 23:30 ` Łukasz Stelmach
2010-03-15 23:49 ` Avery Pennarun
2010-03-15 19:58 ` Chris Packham
2010-03-15 20:01 ` Avery Pennarun [this message]
2010-03-15 23:28 ` Łukasz Stelmach
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=32541b131003151301i69e5df1doc463406738086a89@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=judge.packham@gmail.com \
--cc=lukasz.stelmach@iem.pw.edu.pl \
/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).