remote rename

2014-03-08 Thread Matan Nassau
Hi,

If I have a remote branch origin/topic/foo, running

 $ git remote rename origin renamed

seems to leave directory traces behind: .git/refs/remotes/origin/topic

I expected to see .git/refs/remotes/renamed/topic/foo but not 
.git/refs/remotes/origin. Is this a glitch?

I see this with Git 1.9.0.


Matan--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Bug: commit -p breaks with -m

2013-08-14 Thread Matan Nassau
With git 1.8.3.3,

 $ seq 5 data
 $ git add data
 $ git commit -mdata
 $ sed -i '2 d' data
 $ git commit -pmchange

At the prompt, type e to edit the hunk. The editor doesn't start, but git 
records a commit.

I found that builtin/commit.c sets the GIT_EDITOR env var to : when the user 
specifies the -m option. This was done in 406400ce4f69. Removing these two 
lines,

 if (!use_editor)
 setenv(GIT_EDITOR, :, 1);

seems to fix the issue, but I'm not sure this won't break the 
prepare-commit-msg hook. I'd like to submit a patch: can I get a hint if this 
change would break commit hooks or anything else I'm not seeing?--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html