git commit -> IRC, Bugzilla, email integration.

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

git commit -> IRC, Bugzilla, email integration.

Sourceware - libc-alpha mailing list
We have some integration issues to with git hooks to resolve.

This is a good opportunity to ask the community what they want to see.

Today:

(1) All commits, even on vendor branches, go to glibc-cvs
(2) Only commits to
    refs/heads/master|refs/heads/release/* go to IRC.
(3) Only commits to
    refs/heads/master|refs/heads/release/* go to bugzilla based on bug #.

Should we change (1) to match (2) and (3)?

I know that we decided (2) and (3) to avoid spamming with rebases
or merges on vendor branches.

--
Cheers,
Carlos.

Reply | Threaded
Open this post in threaded view
|

Re: git commit -> IRC, Bugzilla, email integration.

Siddhesh Poyarekar-8
On 18/07/20 02:13, Carlos O'Donell via Libc-alpha wrote:

> We have some integration issues to with git hooks to resolve.
>
> This is a good opportunity to ask the community what they want to see.
>
> Today:
>
> (1) All commits, even on vendor branches, go to glibc-cvs
> (2) Only commits to
>     refs/heads/master|refs/heads/release/* go to IRC.
> (3) Only commits to
>     refs/heads/master|refs/heads/release/* go to bugzilla based on bug #.
>
> Should we change (1) to match (2) and (3)?

I'm for this, but maybe there's a case for differentiating betweeen
vendor namespace branches and user branches for glibc-cvs.  I can
imagine vendor branch commit notifications having a greater-than-one
audience but not user namespace branches.

Siddhesh