{"thread":{"id":"25714","subject":"git clone / git pull to USB memory stick (FAT) and symlinks","startedAt":"2010-11-11T16:35:17Z","lastAt":"2010-11-12T15:59:03Z","messageCount":7,"participants":["Gelonida","Junio C Hamano","Ferry Huberts","Santi Béjar"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"155704","messageId":"ibh605$adm$1@dough.gmane.org","threadId":"25714","inReplyTo":null,"subject":"git clone / git pull to USB memory stick (FAT) and symlinks","fromName":"Gelonida","fromEmail":"gelonida@gmail.com","sentAt":"2010-11-11T16:35:17Z","receivedAt":"2010-11-11T16:35:17Z","isPatch":false,"sender":{"key":"gelonida@gmail.com","avatar":null},"body":"Hi,\n\nFor a given project I'd like to have some USB memory sticks, which I'd\nlike to keep up to date.\n\nI thought about cloning a remote git repository onto the stick\nand performing\n- regular pulls in order to update the USB stick\n- occasional pushes in orderto publish changes performed on the stick.\n\n\nNow my questions:\n\n\n1.) Ignore skip / symlinks\n-----------------------------\nThe git repository might contain symlinks (as it was created on a linux\nhost)\n\nIs there any way to perform a git clone / pull and just skip any symlink\nin the working directory\n\n\n2.) Avoiding file permission issues: Is this sufficient\n---------------------------------------------------------\n\nI read about some config setting which should avoid problems with\nthe rather limited file permissions on a FAT file system\n\ngit config --add core.fileMode false\n\n\n\n3.) Any other special config settings\n-----------------------------------------\nAre there any other special preparations to be done fi I'd like to\nhave a non bare git repository on a memory stick.\n\n\nThanks for your suggestions\n"},{"id":"155715","messageId":"7vk4kjhhjh.fsf@alter.siamese.dyndns.org","threadId":"25714","inReplyTo":"ibh605$adm$1@dough.gmane.org","subject":"Re: git clone / git pull to USB memory stick (FAT) and symlinks","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-11-11T17:54:58Z","receivedAt":"2010-11-11T17:54:58Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Gelonida writes:\n\n> I thought about cloning a remote git repository onto the stick\n> and performing\n> - regular pulls in order to update the USB stick\n> - occasional pushes in orderto publish changes performed on the stick.\n\n... missing is the reason why this is done to a USB memory stick. More\nspecifically,...\n\n> 1.) Ignore skip / symlinks\n> 2.) Avoiding file permission issues: Is this sufficient\n\nThese become non-issues _if_ the reason you are putting this on an USB\nstick is to safekeep and sneakernet the project data, and are not\ninterested in having a working tree on the stick, which I often find is\nthe use case after grilling people who ask about placing git repositories\non an USB stick.\n\nAnd the commands to interact with such a repository without a working tree\nare to \"push\" (into it), and \"fetch\" (from it). IOW, you do not \"pull\"\ninto USB stick.\n\nIf you do need a working tree on the stick, and the stick has a FAT\nderived filesystem (which would be the most common), then you would need\n\n> git config --add core.fileMode false\n\nand perhaps \"core.symlinks false\" also would help\n"},{"id":"155719","messageId":"ibhb64$51p$1@dough.gmane.org","threadId":"25714","inReplyTo":"7vk4kjhhjh.fsf@alter.siamese.dyndns.org","subject":"Re: git clone / git pull to USB memory stick (FAT) and symlinks","fromName":"Gelonida","fromEmail":"gelonida@gmail.com","sentAt":"2010-11-11T18:03:48Z","receivedAt":"2010-11-11T18:03:48Z","isPatch":false,"sender":{"key":"gelonida@gmail.com","avatar":null},"body":"On 11/11/2010 06:54 PM, Junio C Hamano wrote:\n> Gelonida writes:\n> \n>> I thought about cloning a remote git repository onto the stick\n>> and performing\n>> - regular pulls in order to update the USB stick\n>> - occasional pushes in orderto publish changes performed on the stick.\n> \n> ... missing is the reason why this is done to a USB memory stick. More\n> specifically,...\n\nThe idea is to have a few administrator keys .\n\n\nThese administrator keys would be plugged into network less PCs. (no git\ninstalled)\n\n\nI wanted to use git to use these keys up to date.\n\nAs the write speed to USB keys is slow I thought about using git in\norder to avoid copying wrting already up to date config scripts and tools.\n\nOccasionally one might encounter errors in the setup scripts and fix\nthem immediatel with word pad on the targe system.\n\nThus the idea to change files directly on the USB key.\n\nWhen repluging the key nto a development host one could pull / push in\norder to update the central repositroy and all other users just ahd to\npull again to their keys.\n\n\nI hope this explains why I thought about having\n- a non bare repository on a USB stick\n- due to historical reasons some sym links might be in the repository.\n thus my question of how to let git ignore these sym links.\n If this is not possible, then I would probably create a new\n\tsymlink-less git repository\n\n\n> \n>> 1.) Ignore skip / symlinks\n>> 2.) Avoiding file permission issues: Is this sufficient\n> \n> These become non-issues _if_ the reason you are putting this on an USB\n> stick is to safekeep and sneakernet the project data, and are not\n> interested in having a working tree on the stick, which I often find is\n> the use case after grilling people who ask about placing git repositories\n> on an USB stick.\n> \n> And the commands to interact with such a repository without a working tree\n> are to \"push\" (into it), and \"fetch\" (from it). IOW, you do not \"pull\"\n> into USB stick.\n> \n> If you do need a working tree on the stick, and the stick has a FAT\n> derived filesystem (which would be the most common), then you would need\n> \n>> git config --add core.fileMode false\n> \n> and perhaps \"core.symlinks false\" also would help\n"},{"id":"155720","messageId":"ibhbgi$643$1@dough.gmane.org","threadId":"25714","inReplyTo":"7vk4kjhhjh.fsf@alter.siamese.dyndns.org","subject":"Re: git clone / git pull to USB memory stick (FAT) and symlinks","fromName":"Gelonida","fromEmail":"gelonida@gmail.com","sentAt":"2010-11-11T18:09:21Z","receivedAt":"2010-11-11T18:09:21Z","isPatch":false,"sender":{"key":"gelonida@gmail.com","avatar":null},"body":"On 11/11/2010 06:54 PM, Junio C Hamano wrote:\n> Gelonida writes:\n\n> \n> If you do need a working tree on the stick, and the stick has a FAT\n> derived filesystem (which would be the most common), then you would need\n> \n>> git config --add core.fileMode false\n> \n> and perhaps \"core.symlinks false\" also would help\n\nWIll try core,symlinks\n"},{"id":"155722","messageId":"ibhbic$643$2@dough.gmane.org","threadId":"25714","inReplyTo":"7vk4kjhhjh.fsf@alter.siamese.dyndns.org","subject":"Re: git clone / git pull to USB memory stick (FAT) and symlinks","fromName":"Gelonida","fromEmail":"gelonida@gmail.com","sentAt":"2010-11-11T18:10:20Z","receivedAt":"2010-11-11T18:10:20Z","isPatch":false,"sender":{"key":"gelonida@gmail.com","avatar":null},"body":"On 11/11/2010 06:54 PM, Junio C Hamano wrote:\n> Gelonida writes:\n> If you do need a working tree on the stick, and the stick has a FAT\n> derived filesystem (which would be the most common), then you would need\n> \n>> git config --add core.fileMode false\n> \n> and perhaps \"core.symlinks false\" also would help\n\n\nThanks:\n\nWill try core.symlinks false\n"},{"id":"155783","messageId":"4CDD57EB.7050200@hupie.com","threadId":"25714","inReplyTo":"7vk4kjhhjh.fsf@alter.siamese.dyndns.org","subject":"Re: git clone / git pull to USB memory stick (FAT) and symlinks","fromName":"Ferry Huberts","fromEmail":"mailings@hupie.com","sentAt":"2010-11-12T15:06:19Z","receivedAt":"2010-11-12T15:06:19Z","isPatch":false,"sender":{"key":"mailings@hupie.com","avatar":"https://gravatar.com/avatar/ca355376c0713475e17ae413a49f6b98bcbc54cd8364cab7113c53107fb839bb?d=mp&s=160"},"body":"IIRC then a FAT filesystem will screw up your repository.\nIs that still the case?\n\nWe had a few problems with that at work which is why I advised against it.\n\n\n\nOn 11/11/2010 06:54 PM, Junio C Hamano wrote:\n> Gelonida writes:\n>\n>> I thought about cloning a remote git repository onto the stick\n>> and performing\n>> - regular pulls in order to update the USB stick\n>> - occasional pushes in orderto publish changes performed on the stick.\n> ... missing is the reason why this is done to a USB memory stick. More\n> specifically,...\n>\n>> 1.) Ignore skip / symlinks\n>> 2.) Avoiding file permission issues: Is this sufficient\n> These become non-issues _if_ the reason you are putting this on an USB\n> stick is to safekeep and sneakernet the project data, and are not\n> interested in having a working tree on the stick, which I often find is\n> the use case after grilling people who ask about placing git repositories\n> on an USB stick.\n>\n> And the commands to interact with such a repository without a working tree\n> are to \"push\" (into it), and \"fetch\" (from it). IOW, you do not \"pull\"\n> into USB stick.\n>\n> If you do need a working tree on the stick, and the stick has a FAT\n> derived filesystem (which would be the most common), then you would need\n>\n>> git config --add core.fileMode false\n> and perhaps \"core.symlinks false\" also would help\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at http://vger.kernel.org/majordomo-info.html\n\n\ngrtz\n\n-- \nFerry Huberts\n"},{"id":"155785","messageId":"AANLkTik+9WOO12nOUeJB6X8HGor3pJdHW+mrS7KSHuRP@mail.gmail.com","threadId":"25714","inReplyTo":"4CDD57EB.7050200@hupie.com","subject":"Re: git clone / git pull to USB memory stick (FAT) and symlinks","fromName":"Santi Béjar","fromEmail":"santi@agolina.net","sentAt":"2010-11-12T15:59:03Z","receivedAt":"2010-11-12T15:59:03Z","isPatch":false,"sender":{"key":"santi@agolina.net","avatar":null},"body":"Please, do not toppost.\n\nOn Fri, Nov 12, 2010 at 4:06 PM, Ferry Huberts wrote:\n> IIRC then a FAT filesystem will screw up your repository.\n> Is that still the case?\n\nUsing very very old git version, yes. But no for newer git. For the repository.\n\nHTH,\nSanti\n"}]}