OK, I admit it, I want to abuse git. I cloned a library which implements
some functionality. The library is written in Python. I want to "port" this
functionality to Google's Go language. Now, what is probably the correct
thing to do is to simply create a "Go" branch and develop there, leaving
the Python code alone. Perhaps merging the Go branch back into "master"
once the port is working. But I'd really like to create the "Go" branch
with none of the Python files in it and with no "footprints" of the Python
code in the "Go" branch. I know that I could simply create the "Go" branch,
then git rm all the Python code. But I don't really like "cluttering up"
the commit log in the "Go" branch that way.

Perhaps what I need to do is create a separate repository with the "Go"
code. And then, later, somehow "merge" (not git merge) the two repositories
together. Perhaps something like:

cd ~/Library
git fetch file://~/Library-Go/.git Go
git checkout FETCH_HEAD
git checkout -b Go
git checkout -- master .gitignore
# remove files in directory which were in .gitignore from master branch

Or am I totally off-base with this idea of keeping functionally identical
libraries implemented in different language in different branches?

Werner Heisenberg is driving down the autobahn. A police officer pulls
him over. The officer says, "Excuse me, sir, do you know how fast you
were going?"
"No," replies Dr. Heisenberg, "but I know where I am."

Computer Science is the only discipline in which we view adding a new wing
to a building as being maintenance -- Jim Horning

Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.

He's about as useful as a wax frying pan.

Maranatha! <><
John McKown

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/d/optout.

Reply via email to