Mixing
Eclipse Egit - is it possible to compare commits on different projects?
At the new workplace where I work, in the past, the main project was split in two branches, because different customers began to have very different requirements. A pretty common scenario I guess.
Now, I'am not a developer but a sysadmin, and not an expert of git, but I was wondering if in these cases usually is the correct approach to use branches, because in my understanding a fork would be more adapt.
What the CTO is asking me to do, is to migrate this branch, into a new git repository. But he also says that he wants to still be able to perform comparisons between commits, therefore (in eclipse + egit) to right-click on workspace > team > show in history > select the commits he wants to compare > click on compare to each other. I believe that these requirements conflict to each other, so my main question is: is it possible to compare commits of different git repositories?
My second question is, if a project with the same core that starts to require different features, should be branched forked or moved to a new repository?
Hope my question is not too broad
eclipse git branch egit
edited Nov 23 '18 at 10:38
mike
659624
asked Nov 19 '18 at 15:54
lese
357119
add a comment |
At the new workplace where I work, in the past, the main project was split in two branches, because different customers began to have very different requirements. A pretty common scenario I guess.
Now, I'am not a developer but a sysadmin, and not an expert of git, but I was wondering if in these cases usually is the correct approach to use branches, because in my understanding a fork would be more adapt.
What the CTO is asking me to do, is to migrate this branch, into a new git repository. But he also says that he wants to still be able to perform comparisons between commits, therefore (in eclipse + egit) to right-click on workspace > team > show in history > select the commits he wants to compare > click on compare to each other. I believe that these requirements conflict to each other, so my main question is: is it possible to compare commits of different git repositories?
My second question is, if a project with the same core that starts to require different features, should be branched forked or moved to a new repository?
Hope my question is not too broad
eclipse git branch egit
edited Nov 23 '18 at 10:38
mike
659624
asked Nov 19 '18 at 15:54
lese
357119
add a comment |
At the new workplace where I work, in the past, the main project was split in two branches, because different customers began to have very different requirements. A pretty common scenario I guess.
Now, I'am not a developer but a sysadmin, and not an expert of git, but I was wondering if in these cases usually is the correct approach to use branches, because in my understanding a fork would be more adapt.
What the CTO is asking me to do, is to migrate this branch, into a new git repository. But he also says that he wants to still be able to perform comparisons between commits, therefore (in eclipse + egit) to right-click on workspace > team > show in history > select the commits he wants to compare > click on compare to each other. I believe that these requirements conflict to each other, so my main question is: is it possible to compare commits of different git repositories?
My second question is, if a project with the same core that starts to require different features, should be branched forked or moved to a new repository?
Hope my question is not too broad
eclipse git branch egit
edited Nov 23 '18 at 10:38
mike
659624
asked Nov 19 '18 at 15:54
lese
357119
At the new workplace where I work, in the past, the main project was split in two branches, because different customers began to have very different requirements. A pretty common scenario I guess.
Now, I'am not a developer but a sysadmin, and not an expert of git, but I was wondering if in these cases usually is the correct approach to use branches, because in my understanding a fork would be more adapt.
What the CTO is asking me to do, is to migrate this branch, into a new git repository. But he also says that he wants to still be able to perform comparisons between commits, therefore (in eclipse + egit) to right-click on workspace > team > show in history > select the commits he wants to compare > click on compare to each other. I believe that these requirements conflict to each other, so my main question is: is it possible to compare commits of different git repositories?
My second question is, if a project with the same core that starts to require different features, should be branched forked or moved to a new repository?
Hope my question is not too broad
eclipse git branch egit
eclipse git branch egit
edited Nov 23 '18 at 10:38
mike
659624
asked Nov 19 '18 at 15:54
lese
357119
edited Nov 23 '18 at 10:38
mike
659624
asked Nov 19 '18 at 15:54
lese
357119
edited Nov 23 '18 at 10:38
mike
659624
edited Nov 23 '18 at 10:38
mike
659624
edited Nov 23 '18 at 10:38
mike
659624
659624
asked Nov 19 '18 at 15:54
lese
357119
asked Nov 19 '18 at 15:54
lese
357119
asked Nov 19 '18 at 15:54
lese
357119
357119
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
There is no concept called fork in Git. Git hosting services, such as Github or Gitlab, provide such a feature. As far as Git is concerned, a fork is essentially just a branch. And also, every clone of a repository - even local repositories - are essentially forks.
To split up your repository into two repositories that have a fork relationship, first just create a clone of the repository. And then delete branches in both repositories that refer to commits of the now-other-repository.
The usual approach to compare forks is to add a remote to the other remote. This is possible in your case too, since you have common commits in both repositories, before the forking-point. More on remotes here: What is "git remote add ..." and "git push origin master"?
answered Nov 19 '18 at 16:16
alfunx
854313
1.Thank you for your precious answer, I believe that by saying "are essentially forks" in the last part of first paragraph you meant "are essentially branches" : ) 2.Could you please explain better: add a remote to the other remote? should I add a remote on each repository, each one pointing to the other repo? the remote should be of push type, or fetch type? I think fetch type, but just to be sure
– lese
Nov 20 '18 at 12:59
@lese You're right indeed, what I meant to say is that there is little difference between the terms fork and branch, as far as Git is concerned. You got that right, let's say you're onold_repoand want to compare/view commits offork_repo, so you add a remote tofork_repo. As long as you only need read access on thefork_repo, a fetch type remote would be fine.
– alfunx
Nov 20 '18 at 14:38
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378330%2feclipse-egit-is-it-possible-to-compare-commits-on-different-projects%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is no concept called fork in Git. Git hosting services, such as Github or Gitlab, provide such a feature. As far as Git is concerned, a fork is essentially just a branch. And also, every clone of a repository - even local repositories - are essentially forks.
To split up your repository into two repositories that have a fork relationship, first just create a clone of the repository. And then delete branches in both repositories that refer to commits of the now-other-repository.
The usual approach to compare forks is to add a remote to the other remote. This is possible in your case too, since you have common commits in both repositories, before the forking-point. More on remotes here: What is "git remote add ..." and "git push origin master"?
answered Nov 19 '18 at 16:16
alfunx
854313
1.Thank you for your precious answer, I believe that by saying "are essentially forks" in the last part of first paragraph you meant "are essentially branches" : ) 2.Could you please explain better: add a remote to the other remote? should I add a remote on each repository, each one pointing to the other repo? the remote should be of push type, or fetch type? I think fetch type, but just to be sure
– lese
Nov 20 '18 at 12:59
@lese You're right indeed, what I meant to say is that there is little difference between the terms fork and branch, as far as Git is concerned. You got that right, let's say you're onold_repoand want to compare/view commits offork_repo, so you add a remote tofork_repo. As long as you only need read access on thefork_repo, a fetch type remote would be fine.
– alfunx
Nov 20 '18 at 14:38
add a comment |
There is no concept called fork in Git. Git hosting services, such as Github or Gitlab, provide such a feature. As far as Git is concerned, a fork is essentially just a branch. And also, every clone of a repository - even local repositories - are essentially forks.
To split up your repository into two repositories that have a fork relationship, first just create a clone of the repository. And then delete branches in both repositories that refer to commits of the now-other-repository.
The usual approach to compare forks is to add a remote to the other remote. This is possible in your case too, since you have common commits in both repositories, before the forking-point. More on remotes here: What is "git remote add ..." and "git push origin master"?
answered Nov 19 '18 at 16:16
alfunx
854313
1.Thank you for your precious answer, I believe that by saying "are essentially forks" in the last part of first paragraph you meant "are essentially branches" : ) 2.Could you please explain better: add a remote to the other remote? should I add a remote on each repository, each one pointing to the other repo? the remote should be of push type, or fetch type? I think fetch type, but just to be sure
– lese
Nov 20 '18 at 12:59
@lese You're right indeed, what I meant to say is that there is little difference between the terms fork and branch, as far as Git is concerned. You got that right, let's say you're onold_repoand want to compare/view commits offork_repo, so you add a remote tofork_repo. As long as you only need read access on thefork_repo, a fetch type remote would be fine.
– alfunx
Nov 20 '18 at 14:38
add a comment |
There is no concept called fork in Git. Git hosting services, such as Github or Gitlab, provide such a feature. As far as Git is concerned, a fork is essentially just a branch. And also, every clone of a repository - even local repositories - are essentially forks.
To split up your repository into two repositories that have a fork relationship, first just create a clone of the repository. And then delete branches in both repositories that refer to commits of the now-other-repository.
The usual approach to compare forks is to add a remote to the other remote. This is possible in your case too, since you have common commits in both repositories, before the forking-point. More on remotes here: What is "git remote add ..." and "git push origin master"?
answered Nov 19 '18 at 16:16
alfunx
854313
There is no concept called fork in Git. Git hosting services, such as Github or Gitlab, provide such a feature. As far as Git is concerned, a fork is essentially just a branch. And also, every clone of a repository - even local repositories - are essentially forks.
To split up your repository into two repositories that have a fork relationship, first just create a clone of the repository. And then delete branches in both repositories that refer to commits of the now-other-repository.
The usual approach to compare forks is to add a remote to the other remote. This is possible in your case too, since you have common commits in both repositories, before the forking-point. More on remotes here: What is "git remote add ..." and "git push origin master"?
answered Nov 19 '18 at 16:16
alfunx
854313
answered Nov 19 '18 at 16:16
alfunx
854313
answered Nov 19 '18 at 16:16
alfunx
854313
answered Nov 19 '18 at 16:16
alfunx
854313
854313
1.Thank you for your precious answer, I believe that by saying "are essentially forks" in the last part of first paragraph you meant "are essentially branches" : ) 2.Could you please explain better: add a remote to the other remote? should I add a remote on each repository, each one pointing to the other repo? the remote should be of push type, or fetch type? I think fetch type, but just to be sure
– lese
Nov 20 '18 at 12:59
@lese You're right indeed, what I meant to say is that there is little difference between the terms fork and branch, as far as Git is concerned. You got that right, let's say you're onold_repoand want to compare/view commits offork_repo, so you add a remote tofork_repo. As long as you only need read access on thefork_repo, a fetch type remote would be fine.
– alfunx
Nov 20 '18 at 14:38
add a comment |
1.Thank you for your precious answer, I believe that by saying "are essentially forks" in the last part of first paragraph you meant "are essentially branches" : ) 2.Could you please explain better: add a remote to the other remote? should I add a remote on each repository, each one pointing to the other repo? the remote should be of push type, or fetch type? I think fetch type, but just to be sure
– lese
Nov 20 '18 at 12:59
@lese You're right indeed, what I meant to say is that there is little difference between the terms fork and branch, as far as Git is concerned. You got that right, let's say you're onold_repoand want to compare/view commits offork_repo, so you add a remote tofork_repo. As long as you only need read access on thefork_repo, a fetch type remote would be fine.
– alfunx
Nov 20 '18 at 14:38
1.Thank you for your precious answer, I believe that by saying "are essentially forks" in the last part of first paragraph you meant "are essentially branches" : ) 2.Could you please explain better: add a remote to the other remote? should I add a remote on each repository, each one pointing to the other repo? the remote should be of push type, or fetch type? I think fetch type, but just to be sure
– lese
Nov 20 '18 at 12:59
1.Thank you for your precious answer, I believe that by saying "are essentially forks" in the last part of first paragraph you meant "are essentially branches" : ) 2.Could you please explain better: add a remote to the other remote? should I add a remote on each repository, each one pointing to the other repo? the remote should be of push type, or fetch type? I think fetch type, but just to be sure
– lese
Nov 20 '18 at 12:59
@lese You're right indeed, what I meant to say is that there is little difference between the terms fork and branch, as far as Git is concerned. You got that right, let's say you're on
old_repo and want to compare/view commits of fork_repo, so you add a remote to fork_repo. As long as you only need read access on the fork_repo, a fetch type remote would be fine.– alfunx
Nov 20 '18 at 14:38
@lese You're right indeed, what I meant to say is that there is little difference between the terms fork and branch, as far as Git is concerned. You got that right, let's say you're on
old_repo and want to compare/view commits of fork_repo, so you add a remote to fork_repo. As long as you only need read access on the fork_repo, a fetch type remote would be fine.– alfunx
Nov 20 '18 at 14:38
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378330%2feclipse-egit-is-it-possible-to-compare-commits-on-different-projects%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
