FAQ
I just fixed the "playground" and "net" projects. They were the only two
with merge policies instead of cherry-pick.

I see we have at least one merge commit in the net repo:

https://github.com/golang/net/commit/174cd93deca8f4533208a475ec64309cc4619387

I don't know whether this will break various tools (which might assume a
linear history?) like adg's commit watcher program.

Do we want to rewrite history while we still kinda can? I don't know.

Russ?

On Wed, Jan 7, 2015 at 12:00 AM, Dave Cheney wrote:

Hello,

I just noticed that for the subrepos, or at least the /net/ subrepo,
the merge strategy does not default to cherrypick. I've reviewed two
CLs today who have chosen "merge if necessary".

Maybe this needs fixing, IDK, I'm a gerrit noob.

Thanks

Dave
--
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Search Discussions

Discussion Posts

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 4 | next ›
Discussion Overview
groupgolang-dev @
categoriesgo
postedJan 7, '15 at 7:08p
activeJan 8, '15 at 1:31a
posts4
users3
websitegolang.org

People

Translate

site design / logo © 2021 Grokbase