I usually just use patch commits: git add -p
On Tuesday, April 27, 2021 at 10:24:51 AM UTC-4 Reto wrote: > On Mon, Apr 26, 2021 at 11:59:47PM -0700, christoph...@gmail.com wrote: > > Thank you for pointing this out. I wasn’t aware of it. But the question > > still holds for published main programs. > > If you have such a tight dependency that you need to develop them in > parallel > (and hence need replace directives to a local fork) maybe they ought to > life > in the same module? > Then you don't need to have a replace directive in the first place. > > Other than that, git is your friend... *Do* commit the change and then > rebase > the thing away when you don't need it anymore. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/8819e1bd-3b47-4036-802f-a4f8c6dd21b3n%40googlegroups.com.
