IMHO I don't think a third partition will have any effect, but I could be 
very wrong.

I think the problem is a consequence of a couple of things, apologies if 
I'm covering things you already know. There are two things to consider, 
your local repository (Git internal storage) and your local working copy 
(the actual modifiable/readable files). Git will store files in the local 
repository in one way and potentially (depending on config) do file 
conversions when moving data to and from the working copy. When it comes to 
actually pushing your changes to remote repository the contents of the 
repositories are matched, your local working copy is ignored.

So in your case you have two Git commands, one in Windows (Cygwin) and one 
in Linux and they know what EOL/EOF they should be using and they're 
different. By default Git will do no conversion on EOL/EOF when storing and 
retrieving files from the repository (if I remember correctly). The problem 
with this is in your case the two commands (or specifically the Windows 
client) are adjusting the files when they're in your working copy to 
reflect your platforms line ending. I know I'm being a bit vague here, this 
blog post explains things far better - 
http://timclem.wordpress.com/2012/03/01/mind-the-end-of-your-line/

Now in the specific case of your ogg files, possibly Git is not detecting 
them properly as binary files and the files happen contain bytes which are 
CRLF, LF, etc. and although they don't have that meaning in the files Git 
thinks they do. So I would add a .gitattributes files (as described in the 
blog post) to your local repository (and possibly the remote one too) and 
it'll mean *all* clients will behave appropriately. So specifically you 
want to tell Git that the ogg files are binary and so it will leave them 
alone.

HTH

On Thursday, 31 January 2013 01:34:53 UTC, Matthew Johnson wrote:
>
> Please explain why I would need a third partition to do this. I am not 
> aware of any restrictions in Git concerning what machine/partition the 
> workspace and repository must live on, except that the remote is expected 
> to really be remote, i.e., not on the local machine, accessible only over 
> the net, whether via git:// scheme or some other. And why would files be 
> "changed when you jump back and forth"? If both the workspace and 
> repository are one and the same partition, why would it make any difference 
> which filesystem it is mounted on or accessed from? The same .git files are 
> being read, the same submitted files, etc.
>
> BTW: I am trying to do both the things you mention: keep one work area I 
> can use from either Windows or Linux and keep a remote repo I can get to 
> from both (upstream). The latter is already achieved, it is the first that 
> is giving me strange discrepancies concerning which files are modified.
>
> Because of this discrepancy, though I continue to edit files running 
> either Windows or Fedora, I do the revision control only while running 
> Windows. But this is far from ideal, especially when it looks like I am so 
> close to getting the ability to run Git correctly from either.
>
> BTW: the remote repository is at Github. But since I am so underwhelmed by 
> their GUI, I stick to command line Git whenever possible: the Git 
> documentation is good enough that I have a much better idea what is really 
> going on when I execute a Git command on the command line, despite the 
> problem I am having with these dubious 'modified' reports.
>
> On Wednesday, January 30, 2013 9:24:26 AM UTC-8, John Fisher wrote:
>>
>> Matthew, I defer to actual Git experts... but heres some sysadmin ideas:
>>
>> Are you trying to keep one work area you can use for Windows and for Linux? 
>> Or are you trying to keep a remote repos
>> which you can get to from both?
>>
>> If you create a third partition and put your Git workarea and repository 
>> there, then you could mount it from both
>> Windows and Linux. But files are going be changed when you jump back and 
>> forth. You could also switch to running Linux,
>> and put up a VM of Windows ( or vice versa) and have both running at once, 
>> keeping your remote repos on Linux and having
>> two work areas. Or, you could get that old Pentium4/ Pentium/ AMD dog out of 
>> the closet or for $25 at the thrift store,
>> and set up a Linux server with a remote repository. Or you could host your 
>> project at github.
>>
>> John
>>
>>
>>
>> On Tuesday, January 29, 2013 6:40:47 PM UTC-8, Matthew Johnson wrote:
>>>
>>>
>>>
>>> First, some background. I have one hard disk separated into two partitions: 
>>> one for the version of Windows 7 that shipped on this rather new 
>>> Thinkpad (Windows 7 Professional SP1), the other for Fedora 17 (which I 
>>> installed and keep up-to-date). Of course, it is rather easy to access 
>>> the Windows partition from the F17 partition, which I
>>> have been doing with no noticeable problems: 
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to