From: Sajan Parikh <sajan@parikh.io>
To: git@vger.kernel.org
Subject: Syncing Git Repositories
Date: Wed, 16 Jul 2014 21:26:07 -0500 [thread overview]
Message-ID: <53C7343F.4090806@parikh.io> (raw)
[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]
On all my laptops and desktops, I have a directory at /home/sajan/Code
where all my active projects and repositories live.
/home/sajan/Code/repository1
/home/sajan/Code/repository2
/home/sajan/Code/repository3
...etc...
Up until now I've relied on pushing and pulling to and from my Gitlab
server to keep my projects in sync across all my laptops and desktops.
It's worked great.
However, today I decided to add my code folder to my ownCloud server and
sync it across all my laptops and desktops the same way I do for
/home/sajan/Documents, /home/sajan/Music, and a few application config
directories to keep all my devices in sync.
By syncing my code folder and git repositories in this way, do I risk
borking any repositories? I'm 99% confident I'm not, since everything
is in .git/, and there are not external databases or log files that need
to be updated. Just making sure though.
I'm only doing this because sometimes I forget to pull changes down from
my Gitlab server on a different laptop or desktop and start making local
changes. Which is fine, I can merge easily, but if everything were
sync'd automatically when I logged into my computer it would be great.
Another option I thought of would be to write a bash script that
executed at login and went into each of my repositories and ran git
pull, but I decided against this because of legitimate non-fast-forward
merges.
TLDR;
If I sync my repositories across computers using something similar to
Dropbox, rather than pushing/pulling to and from an central repository,
am I risking borking any respository?
--
Sajan Parikh
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3195 bytes --]
next reply other threads:[~2014-07-17 3:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 2:26 Sajan Parikh [this message]
2014-07-17 6:53 ` Syncing Git Repositories Matthieu Moy
2014-07-17 16:35 ` Junio C Hamano
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=53C7343F.4090806@parikh.io \
--to=sajan@parikh.io \
--cc=git@vger.kernel.org \
/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).