Re: Using git-replace in place of grafts -- and publishing .git/refs/replace between repos?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



David Chanters <david.chanters@xxxxxxxxxxxxxx> writes:

> I've tried:
>
> [remote "origin"]
>         fetch =
> +refs/replace/*:+refs/heads/*:refs/remotes/origin/*:refs/replace/*

Read the documentation and learn about <refspec> instead of blindly
guessing.

	[remote "origin"]
		fetch = +refs/heads/*:refs/remotes/origin/*
	        fetch = +refs/replace/*:refs/replace/*

would be syntactically more correct.  That would blindly fetch each
and every replace refs from the other side and apply the replacement.

It is questionable if it is a sensible thing to do, though.

"Git cabal" has been discussing a plan to make this easier but it is
not quite ready to outline here yet.  Perhaps after I return from my
vacation post 1.8.0 release ;-)
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]