Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: Re-integrate an already extracted subtree that still exists in the source #8

Open
wants to merge 12 commits into
base: master
Choose a base branch
from

Conversation

sun
Copy link

@sun sun commented Dec 15, 2011

Note: I've absolutely no idea whether this is correct, or whether it's totally superfluous. Please comment accordingly. Feedback welcome!

Note: This is based on the sun:docs branch. Merge that first.

Use-case being:

  1. You have an original/mainline repo that contains some library code that could be extracted into its own public repo.
  2. You extract the library code from mainline using common/usual commands to perform the task [1], which means you have two repos that contain the history of the library now.
  3. You realize that git-subtree exists. (d'oh!) You want to use it in the future.
  4. You want to merge any upstream changes in the library back into the mainline, and also merge any (future) changes to the library in the mainline to the upstream library.
  5. To execute 4. you follow the commands outlined in the added example for re-integrating an already extracted subtree that still exists in the source (mainline).

[1] http://stackoverflow.com/questions/359424/detach-subdirectory-into-separate-git-repository

Vanuan and others added 12 commits August 12, 2010 18:21
Description: Made the difference from submodules and the subtree
merge strategy clearer.

Synopsys and options: Synchronize with 'git subtree -h' output.
I hope, properly.

Examples: Added example descriptions in captions. Small fixes.

Signed-off-by: John Yani <[email protected]>
Merge remote-tracking branch 'remotes/thomasvandoren/master' into docs

Conflicts:
	INSTALL
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants