Re: Add "clone" support to lntree

Dear diary, on Sat, Apr 16, 2005 at 03:56:03AM CEST, I got a letter where Daniel Barkalow <barkalow@iabervon.org> told me that...

I'm sorry but you are late, I added it about a hour and half ago or so. :-) Check git fork. (I *want* separate command than git lntree. In fact, I think I should make git lntree gitXlntree.sh instead, since it is really internal command for git-tools and the user should probably never need it for anything. git lntree is too lowlevel.)

Actually, I don't like the name at all, though. Some people may find pondering about names pointless, but when I'm going to type them in every day for the rest of my life, they better should not be stupid. ;-)

So, what are your clever ideas about git fork's proper name? Or should we leave it as is?

Summary of current related git commands (yes, they are already around and should be actually all working):

	git addremote --- registers a remote branch (name - URL pair)
	git branch --- creates a branch from a given commit
			(when passed empty commit, creates a branch
			from the current commit and sets the working
			tree to that branch)
	git clone --- creates a local GIT repository from a remote one
	git export --- checks out given commit to a separate directory
			(without any GIT information)
	git fork --- creates a new branch and working tree from
			the current working tree, sharing the same
			local GIT repository
	git lntree --- creates a "treeshell" sharing the same GIT
			repository with the current tree

If you think any other of those should be renamed, this is the time to speak up. Oh well, I think I'll regret asking about this at all... ;-)

Note that there is a bug in current git update - it will allow you to bring several of your trees to follow the same branch, or even a remote branch. This is not even supposed to work, and will be fixed when I get some sleep. You will be able to do git pull even on local branches, and the proper solution for this will be just tracking the branch you want to follow.

So, I'll fix that tomorrow, enable you to fork to an existing but unused branch, fix git pull of remote branch by several local branches, and write a lot of documentation.

Kind regards,