On Wed, Aug 31, 2011 at 02:19:08PM +0300, Paul Sokolovsky wrote:
> Hello Christian,
>
> On Tue, 30 Aug 2011 12:43:40 -0300
> Christian Robottom Reis <kiko@linaro.org> wrote:
>
> > On Tue, Aug 30, 2011 at 01:25:15PM +0300, Paul Sokolovsky wrote:
> > > Yeah, I have patch for that. But we cannot use before upstream
> > > accepts it (because people will get errors checking out tree) and I
> > > don't hold my breath for that at all.
> >
> > Why wouldn't we provide our own version of repo that worked around
> > this issue?
>
> By the same reason we don't fork entire Android itself and fixing it to
> work "right"? ;-)

Either I'm missing the point or you are. We "fork" Android and
everything else all the time; we then proceed to send the patches
upstream and help them through the process, and so for me the "fork" is
more like a cooperative branch.

Look, this is a weird conversation and I want to get out of it as soon
as I can. But you guys are overblowing the issue -- I'm just suggesting
that if the patch will take a while to go upstream, you can ship a
separate repo tool. We do this all the time in Linaro (just look at
www.linaro.org/downloads).

I agree with kiko here. If the repo patch would have a clearer indication in gerrit by now that this is not acceptable upstream I would have agreed to think about a solution on the git branch policy side. But if the lack of --tag hurts us now badly we should work around somehow by patching repo etc. until that patch discussion gives us more assurance that adopting everyone's workflow is not just for the sake of a temporary bandaid.