Mixing
Copy Git Repos to another machine
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I want to copy all my git repos from my old machine to my new machine (both Ubuntu). I will keep using both machines... I am doing this out of sheer laziness, (and maybe for some local branches and stashes at hand), but I could just as well freshly clone from the various upstream repositories...
Question: Is this harmful in some way?
(Of course the repo states should be binary identical, whether I copy files or go for git clone. But I could imagine, git puts some kind of unique (g)uuid into the .git folder upon first clone or so, to distinguish machines or such... but just a guess. I simply don't know the inner workings...)
update:
my fear is primarily around uuids or similar, non-uniqueness of then two local git 'repos' ("clients") towards one remote repo ("master/server").
If you know about this being ok or not-ok, I need actual sources for that knowledge (beyond „I believe“).
That being said, I think I found a duplicate of my question on Superuser.
backup git copy cloning
asked 5 hours ago
Frank Nocke
341413
add a comment |Â
up vote
1
down vote
favorite
I want to copy all my git repos from my old machine to my new machine (both Ubuntu). I will keep using both machines... I am doing this out of sheer laziness, (and maybe for some local branches and stashes at hand), but I could just as well freshly clone from the various upstream repositories...
Question: Is this harmful in some way?
(Of course the repo states should be binary identical, whether I copy files or go for git clone. But I could imagine, git puts some kind of unique (g)uuid into the .git folder upon first clone or so, to distinguish machines or such... but just a guess. I simply don't know the inner workings...)
update:
my fear is primarily around uuids or similar, non-uniqueness of then two local git 'repos' ("clients") towards one remote repo ("master/server").
If you know about this being ok or not-ok, I need actual sources for that knowledge (beyond „I believe“).
That being said, I think I found a duplicate of my question on Superuser.
backup git copy cloning
asked 5 hours ago
Frank Nocke
341413
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I want to copy all my git repos from my old machine to my new machine (both Ubuntu). I will keep using both machines... I am doing this out of sheer laziness, (and maybe for some local branches and stashes at hand), but I could just as well freshly clone from the various upstream repositories...
Question: Is this harmful in some way?
(Of course the repo states should be binary identical, whether I copy files or go for git clone. But I could imagine, git puts some kind of unique (g)uuid into the .git folder upon first clone or so, to distinguish machines or such... but just a guess. I simply don't know the inner workings...)
update:
my fear is primarily around uuids or similar, non-uniqueness of then two local git 'repos' ("clients") towards one remote repo ("master/server").
If you know about this being ok or not-ok, I need actual sources for that knowledge (beyond „I believe“).
That being said, I think I found a duplicate of my question on Superuser.
backup git copy cloning
asked 5 hours ago
Frank Nocke
341413
I want to copy all my git repos from my old machine to my new machine (both Ubuntu). I will keep using both machines... I am doing this out of sheer laziness, (and maybe for some local branches and stashes at hand), but I could just as well freshly clone from the various upstream repositories...
Question: Is this harmful in some way?
(Of course the repo states should be binary identical, whether I copy files or go for git clone. But I could imagine, git puts some kind of unique (g)uuid into the .git folder upon first clone or so, to distinguish machines or such... but just a guess. I simply don't know the inner workings...)
update:
my fear is primarily around uuids or similar, non-uniqueness of then two local git 'repos' ("clients") towards one remote repo ("master/server").
If you know about this being ok or not-ok, I need actual sources for that knowledge (beyond „I believe“).
That being said, I think I found a duplicate of my question on Superuser.
backup git copy cloning
backup git copy cloning
asked 5 hours ago
Frank Nocke
341413
asked 5 hours ago
Frank Nocke
341413
edited 17 mins ago
asked 5 hours ago
Frank Nocke
341413
asked 5 hours ago
Frank Nocke
341413
asked 5 hours ago
Frank Nocke
341413
341413
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
2
down vote
There is nothing wrong with repository move from one machine to another.
Git will update its internal configurations (if needed) on first run into the repo.
Maybe you can ask yourself why you need to move a repository like a normal folder, if your codebase needs things that are not included in a clean clone from remote then you're probably doing something wrong.
If you concerns are about project configuration files consider that probably on your new machine you'll have to recreate databases or change path or similar so there's no point in keeping old configurations for your project, start fresh and go clean.
answered 4 hours ago
Luigi Pressello
1212
New contributor
Luigi Pressello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
1
down vote
No harm. I recommend using rsync, but tar or cp will do just as well.
answered 4 hours ago
ptman
18.5k12042
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
There is nothing wrong with repository move from one machine to another.
Git will update its internal configurations (if needed) on first run into the repo.
Maybe you can ask yourself why you need to move a repository like a normal folder, if your codebase needs things that are not included in a clean clone from remote then you're probably doing something wrong.
If you concerns are about project configuration files consider that probably on your new machine you'll have to recreate databases or change path or similar so there's no point in keeping old configurations for your project, start fresh and go clean.
answered 4 hours ago
Luigi Pressello
1212
New contributor
Luigi Pressello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
2
down vote
There is nothing wrong with repository move from one machine to another.
Git will update its internal configurations (if needed) on first run into the repo.
Maybe you can ask yourself why you need to move a repository like a normal folder, if your codebase needs things that are not included in a clean clone from remote then you're probably doing something wrong.
If you concerns are about project configuration files consider that probably on your new machine you'll have to recreate databases or change path or similar so there's no point in keeping old configurations for your project, start fresh and go clean.
answered 4 hours ago
Luigi Pressello
1212
New contributor
Luigi Pressello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
2
down vote
up vote
2
down vote
There is nothing wrong with repository move from one machine to another.
Git will update its internal configurations (if needed) on first run into the repo.
Maybe you can ask yourself why you need to move a repository like a normal folder, if your codebase needs things that are not included in a clean clone from remote then you're probably doing something wrong.
If you concerns are about project configuration files consider that probably on your new machine you'll have to recreate databases or change path or similar so there's no point in keeping old configurations for your project, start fresh and go clean.
answered 4 hours ago
Luigi Pressello
1212
New contributor
Luigi Pressello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
There is nothing wrong with repository move from one machine to another.
Git will update its internal configurations (if needed) on first run into the repo.
Maybe you can ask yourself why you need to move a repository like a normal folder, if your codebase needs things that are not included in a clean clone from remote then you're probably doing something wrong.
If you concerns are about project configuration files consider that probably on your new machine you'll have to recreate databases or change path or similar so there's no point in keeping old configurations for your project, start fresh and go clean.
answered 4 hours ago
Luigi Pressello
1212
New contributor
Luigi Pressello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 4 hours ago
Luigi Pressello
1212
New contributor
Luigi Pressello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 4 hours ago
Luigi Pressello
1212
answered 4 hours ago
Luigi Pressello
1212
1212
New contributor
Luigi Pressello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Luigi Pressello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Luigi Pressello is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
add a comment |Â
up vote
1
down vote
No harm. I recommend using rsync, but tar or cp will do just as well.
answered 4 hours ago
ptman
18.5k12042
add a comment |Â
up vote
1
down vote
No harm. I recommend using rsync, but tar or cp will do just as well.
answered 4 hours ago
ptman
18.5k12042
add a comment |Â
up vote
1
down vote
up vote
1
down vote
No harm. I recommend using rsync, but tar or cp will do just as well.
answered 4 hours ago
ptman
18.5k12042
No harm. I recommend using rsync, but tar or cp will do just as well.
answered 4 hours ago
ptman
18.5k12042
answered 4 hours ago
ptman
18.5k12042
answered 4 hours ago
ptman
18.5k12042
answered 4 hours ago
ptman
18.5k12042
18.5k12042
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f936408%2fcopy-git-repos-to-another-machine%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
