Thread (22 messages) flat view 22 messages, 9 authors, 2016-08-11

Re: git-show --stat on first commit

From: Petr Baudis <hidden>
Date: 2016-08-11 20:28:15

On Tue, Nov 21, 2006 at 07:39:56PM CET, Andy Parkins wrote:
On Tuesday 2006, November 21 18:21, Petr Baudis wrote:
quoted
(The answer is usually "create the branch in a separate repo and then
fetch it to the original one". But it feels a bit kludgy given the
otherwise seamless support for unrelated branches. (Not that I ever was
a big fan of unrelated long-lived branches in general.))
Just as kludgy, but I did this today by writing the name of the new branch 
in .git/HEAD then doing

for file in $(git-ls-files); do git-update-index --force-remove $file; done

Before creating the new files and "git-commit"ing.
Ok, this approach looks actually reasonable (contrary to the frequently
suggested rm approach, which is rather dangerous).

Perhaps git checkout --empty could do this?

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
The meaning of Stonehenge in Traflamadorian, when viewed from above, is:
"Replacement part being rushed with all possible speed."
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help