Submit repo status

[Volker Simonis]

The problem you'll run into when you create new clones from time to
time is that a single push from somebody who didn't realize that you
have created a new clone (and didn't recreate its local version of
submit) can unintentionally push ALL the old branches from his local
clone when he only wants to push his single, new
 branch. I actually wonder that this hasn't happened already ...

On Fri, Dec 7, 2018 at 11:17 PM Stanislav Smirnov
<stanislav.smirnov at oracle.com> wrote:
>
> Thank you for your suggestions!
>
> Talking about the branches, as always we ask users to be respectful and try not to forget to close them after they are no longer needed.
> From our side we will consider different options to make sure the repo is in a good shape.
>
> Best regards,
> Stanislav Smirnov
>
> On Dec 6, 2018, at 7:48 AM, Roman Kennke <roman at kennke.org> wrote:
>
> The submit repo was not working as expected last couple of days.
> The main reason is that the "hg pull" operation was not able to complete succesfully because of the number of heads in the repository.
> The submit repo hasn't been "cleaned" since it opened a year ago.
> There are currently 406 (closed + normal) branches in the repo and most of them are “dead” (not active, but have not been closed).
>
> It was decided to start "resetting" the jdk/submit repository regularly.
>
>
> Another possibility would be to automatically close branches which
> match a JBS ID once the corresponding change has been pushed to
> jdk/jdk (the same way JBS issues get "Resloved" automatically once the
> corresponding change gets pushed).
>
>
> Yeah, *that* would seem most useful. I tried hard to exercise hygiene on
> this, but it's easy to forget. A cron-job (or so) that queries all heads
> and checks JBS ID, and closes branches for closed issues seems most
> useful. Is that what is meant by resetting? I just hope it doesn't mean
> we have to clone a fresh new jdk/submit every week/month or so..
>
> Roman
>
>
>