Re: [git-users] connectng 2 win PCs in local network - clone folder to other PC
If you are on an internal 'local (file) network' I would expect that you can simply use the URL that you would use to look at the same folder with Win Explorer, e.g. \\PC-3\OtherGuy\HisRepo (note this uses the windows backslash separator) I use this method with Git Extensions and Git for Windows (msysgit compiled) at work. It doesn't need usernames or passwords as teh permissions are done by the file system. If you are accessing via an intranet, or are using Cygwin then the linux style is more likely, and don't forget to munge (adjust) the colon in C: - Original Message - From: Leonidas Savvides To: Philip Oakley Sent: Sunday, April 07, 2013 6:43 AM Subject: Re: [git-users] connectng 2 win PCs in local network - clone folder to other PC YES IT HELPS... I CLONE COMMAND should be like this or... git clone User-HP@192.168.10.11:C:/Users/User/Documents/PhoneGap/trnotes theProject trnotes dir from which to send - source theProject receive dir / from this executed in CLI - destined User-HP@192.168.10.11username of SOURCE PC and LAN IP WELL IS CORRECT? On Sat, Apr 6, 2013 at 4:51 PM, Philip Oakley philipoak...@iee.org wrote: From nothing. Simply start with `git init` on the first PC. (and `git add`; `git commit` etc. so you have something in the repo) Permit sharing. Got to second (or third, 4th, ..) PC, create directory, permit sharing, and then `git clone`. This should populate the directory with the 'copy' of the remote PC-1. Create and checkout your development branch for that PC-n. Note that you do not have a central bare repository machine. All your remotes are working machines, so there is a potential for collision if one person tries to push a branch that is checked out (and possibly dirty with in-work, uncommitted changes) on the remote machine. I believe git will refuse, but I'm not sure. You can now 'push' that branch back to PC-1, and 'fetch' from PC-1 any work they did. Like wise you can push work from PC-2 to PC-4 if they are want to exchange work on a feature they are working on (and fetch back) I would advice never to 'pull' in this situation as it attempts an auto merge, but to do a distinct two step of 'fetch' and then 'merge'. It gives you a breathing space just in case. (option to require it to be a ff, and clean tree?) Designate one machine as the location of the primary reference for which ever branch you end up using as master, and set up some admin to stage those updates gracefully with team emails to notify when updates are in place. Does that help? - Original Message - From: Leonidas Savvides lsepolis...@gmail.com To: git-users@googlegroups.com Sent: Saturday, April 06, 2013 2:07 PM Subject: Re: [git-users] connectng 2 win PCs in local network - clone folder to other PC What command to use for the push / copy? Also both directories must have .git folder... Initialized with git? Source PC is win7, and destined PC vista both 64bit. -- No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.3272 / Virus Database: 3162/6228 - Release Date: 04/06/13 -- 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.
[git-users] Re: CRLF will be replaced by LF warning
Hi Alexandru, thanks for your reply! Am 2013-04-06 11:55, schrieb Alexandru Pătrănescu: Even if you work on windows, I suggest using core.autocrlf = input, Well, unfortunately, it doesn't help: d:\Dev\Cafu git diff [...] warning: CRLF will be replaced by LF in Libs/TypeSys.cpp. The file will have its original line endings in your working directory. warning: CRLF will be replaced by LF in Libs/TypeSys.hpp. The file will have its original line endings in your working directory. d:\Dev\Cafu git config core.autocrlf false d:\Dev\Cafu git config core.autocrlf input d:\Dev\Cafu git config core.autocrlf input d:\Dev\Cafu git diff [...] warning: CRLF will be replaced by LF in Libs/TypeSys.cpp. The file will have its original line endings in your working directory. warning: CRLF will be replaced by LF in Libs/TypeSys.hpp. The file will have its original line endings in your working directory. More importantly, it seems that core.autocrlf should not affect files covered by the .gitattributes settings at all (if I understood the .gitattributes man page and http://timclem.wordpress.com/2012/03/01/mind-the-end-of-your-line/ correctly). So I still need help with this problem. Best regards, Carsten -- Dipl.-Inf. Carsten Fuchs Carsten Fuchs Software Industriegebiet 3, c/o Rofu, 55768 Hoppstädten-Weiersbach, Germany Internet: http://www.cafu.de | E-Mail: i...@cafu.de Cafu - the open-source game and graphics engine for multiplayer 3D action -- 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.
Re: [git-users] connectng 2 win PCs in local network - clone folder to other PC
Please use reply all to copy in the git user list, so other can pick up the information. IP: On my work servers they are available by name (as are all the shared PCs), so I can use \\PC-1 to refer to a PC rather than by it's internal IP address, and importantly, I didn't need a transport protocol, so it was just accessing and serving files (Windows network) as if it was a local disc. Switching to a protocol changes Git's options so that it expects to 'talk' with the server (except file:// where it simply changes the level of checking)) It will depend on your network setup and it's management (and wether others have already done the hard work to make it a walled garden). Philip - Original Message - From: Leonidas Savvides To: Philip Oakley Sent: Sunday, April 07, 2013 12:47 PM Subject: Re: [git-users] connectng 2 win PCs in local network - clone folder to other PC Ip needed? On Apr 7, 2013 1:02 PM, Philip Oakley philipoak...@iee.org wrote: If you are on an internal 'local (file) network' I would expect that you can simply use the URL that you would use to look at the same folder with Win Explorer, e.g. \\PC-3\OtherGuy\HisRepo (note this uses the windows backslash separator) I use this method with Git Extensions and Git for Windows (msysgit compiled) at work. It doesn't need usernames or passwords as teh permissions are done by the file system. If you are accessing via an intranet, or are using Cygwin then the linux style is more likely, and don't forget to munge (adjust) the colon in C: - Original Message - From: Leonidas Savvides To: Philip Oakley Sent: Sunday, April 07, 2013 6:43 AM Subject: Re: [git-users] connectng 2 win PCs in local network - clone folder to other PC YES IT HELPS... I CLONE COMMAND should be like this or... git clone User-HP@192.168.10.11:C:/Users/User/Documents/PhoneGap/trnotes theProject trnotes dir from which to send - source theProject receive dir / from this executed in CLI - destined User-HP@192.168.10.11username of SOURCE PC and LAN IP WELL IS CORRECT? On Sat, Apr 6, 2013 at 4:51 PM, Philip Oakley philipoak...@iee.org wrote: From nothing. Simply start with `git init` on the first PC. (and `git add`; `git commit` etc. so you have something in the repo) Permit sharing. Got to second (or third, 4th, ..) PC, create directory, permit sharing, and then `git clone`. This should populate the directory with the 'copy' of the remote PC-1. Create and checkout your development branch for that PC-n. Note that you do not have a central bare repository machine. All your remotes are working machines, so there is a potential for collision if one person tries to push a branch that is checked out (and possibly dirty with in-work, uncommitted changes) on the remote machine. I believe git will refuse, but I'm not sure. You can now 'push' that branch back to PC-1, and 'fetch' from PC-1 any work they did. Like wise you can push work from PC-2 to PC-4 if they are want to exchange work on a feature they are working on (and fetch back) I would advice never to 'pull' in this situation as it attempts an auto merge, but to do a distinct two step of 'fetch' and then 'merge'. It gives you a breathing space just in case. (option to require it to be a ff, and clean tree?) Designate one machine as the location of the primary reference for which ever branch you end up using as master, and set up some admin to stage those updates gracefully with team emails to notify when updates are in place. Does that help? - Original Message - From: Leonidas Savvides lsepolis...@gmail.com To: git-users@googlegroups.com Sent: Saturday, April 06, 2013 2:07 PM Subject: Re: [git-users] connectng 2 win PCs in local network - clone folder to other PC What command to use for the push / copy? Also both directories must have .git folder... Initialized with git? Source PC is win7, and destined PC vista both 64bit. -- No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.3272 / Virus Database: 3162/6228 - Release Date: 04/06/13 No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.3272 / Virus Database: 3162/6229 - Release Date: 04/06/13 -- 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.
Re: [git-users] connectng 2 win PCs in local network - clone folder to other PC
On Sun, 7 Apr 2013 11:03:02 +0100 Philip Oakley philipoak...@iee.org wrote: If you are on an internal 'local (file) network' I would expect that you can simply use the URL that you would use to look at the same folder with Win Explorer, e.g. \\PC-3\OtherGuy\HisRepo (note this uses the windows backslash separator) I use this method with Git Extensions and Git for Windows (msysgit compiled) at work. It doesn't need usernames or passwords as teh permissions are done by the file system. ^^^ This is a gross oversimplification which might mislead the OP. In fact the file system kicks in only after the SMB (or CIFS, if you wish to call it this way) protocol did authentication and authorization (if OtherGuy is a shared folder on \\PC-3 then it has its own security settings associated with it which are applied before the file system is accessed). Hence when one works with SMB shares on a Windows network using Git, one still has to think about the authen/authz stuff. Either pass-through authentication must work or the target share must be configured to allow passwordless (guest) access or one has to first connect to the share by hand (via `net use` or using Explorer) with correct credentials and once the authentication is complete and the connection is cached one can run Git to access the resource. -- 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.
Re: [git-users] connectng 2 win PCs in local network - clone folder to other PC
From: Konstantin Khomoutov flatw...@users.sourceforge.net Sent: Sunday, April 07, 2013 5:43 PM On Sun, 7 Apr 2013 11:03:02 +0100 Philip Oakley philipoak...@iee.org wrote: ... uses the windows backslash separator) I use this method with Git Extensions and Git for Windows (msysgit compiled) at work. It doesn't need usernames or passwords as teh permissions are done by the file system. ^^^ This is a gross oversimplification which might mislead the OP. I was giving it as a weighted simplification, given that the OP (Leonidas) had specifically stated that the example PCs were both Windows. I know many git folks are fans of Linux, but the Windows hordes are't far behind. ;-) In fact the file system kicks in only after the SMB (or CIFS, if you wish to call it this way) protocol did authentication and authorization (if OtherGuy is a shared folder on \\PC-3 then it has its own security settings associated with it which are applied before the file system is accessed). Hence when one works with SMB shares on a Windows network using Git, one still has to think about the authen/authz stuff. Either pass-through authentication must work or the target share must be configured to allow passwordless (guest) access or one has to first connect to the share by hand (via `net use` or using Explorer) with correct credentials and once the authentication is complete and the connection is cached one can run Git to access the resource. All reasonable comments if Leonidas is on a mixed network. Many thanks Konstantin. Philip -- 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.
