[bug#61437] [PATCH] doc: contributing: Cover push frequency in the Commit Policy.

[bug#61437] [PATCH] doc: contributing: Cover push frequency in the Commit Policy.

[Christopher Baines]

* doc/contributing.texi (Commit Access): Add paragraph about push frequency.
---
 doc/contributing.texi | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/contributing.texi b/doc/contributing.texi
index c436bc4a31..09b9da3e89 100644
--- a/doc/contributing.texi
+++ b/doc/contributing.texi
@@ -1852,6 +1852,12 @@ commits that caused immediate problems.  This is subject to being
 adjusted, allowing individuals to commit directly on non-controversial
 changes on parts they’re familiar with.
 
+Try to plan ahead and avoid pushing several times in a short time
+window.  This reduces the likelyhood that others working on the same
+branch will encounter problems when pushing.  It also reduces the load
+on services like @url{https://data.guix.gnu.org,data.guix.gnu.org} that
+process each revision that is pushed.
+
 When pushing a commit on behalf of somebody else, please add a
 @code{Signed-off-by} line at the end of the commit log message---e.g.,
 with @command{git am --signoff}.  This improves tracking of who did
-- 
2.38.1

[bug#61437] [PATCH] doc: contributing: Cover push frequency in the Commit Policy.

[Simon Tournier]

Hi,

On sam., 11 févr. 2023 at 21:15, Christopher Baines <mail@cbaines.net> wrote:

> +Try to plan ahead and avoid pushing several times in a short time
> +window.  This reduces the likelyhood that others working on the same
> +branch will encounter problems when pushing.  It also reduces the load
> +on services like @url{https://data.guix.gnu.org,data.guix.gnu.org} that
> +process each revision that is pushed.

The point is to push by batch instead of pushing several times in a row,
right?


Cheers,
simon

[bug#61437] [PATCH] doc: contributing: Cover push frequency in the Commit Policy.

[Christopher Baines]

[-- Attachment #1: Type: text/plain, Size: 758 bytes --]


Simon Tournier <zimon.toutoune@gmail.com> writes:

> Hi,
>
> On sam., 11 févr. 2023 at 21:15, Christopher Baines <mail@cbaines.net> wrote:
>
>> +Try to plan ahead and avoid pushing several times in a short time
>> +window.  This reduces the likelyhood that others working on the same
>> +branch will encounter problems when pushing.  It also reduces the load
>> +on services like @url{https://data.guix.gnu.org,data.guix.gnu.org} that
>> +process each revision that is pushed.
>
> The point is to push by batch instead of pushing several times in a row,
> right?

Pretty much, it's a balance of course as sometimes it'll be worth
pushing without much time between, but as I say there's advantages in
trying to plan ahead to reduce that.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

[bug#61437] [PATCH] doc: contributing: Cover push frequency in the Commit Policy.

[Simon Tournier]

Hi Chris,

On ven., 17 févr. 2023 at 18:36, Christopher Baines <mail@cbaines.net> wrote:

>>> +Try to plan ahead and avoid pushing several times in a short time
>>> +window.  This reduces the likelyhood that others working on the same
>>> +branch will encounter problems when pushing.  It also reduces the load
>>> +on services like @url{https://data.guix.gnu.org,data.guix.gnu.org} that
>>> +process each revision that is pushed.
>>
>> The point is to push by batch instead of pushing several times in a row,
>> right?
>
> Pretty much, it's a balance of course as sometimes it'll be worth
> pushing without much time between, but as I say there's advantages in
> trying to plan ahead to reduce that.

Well, maybe it is only me but I have difficulties to understand what you
mean by “plan ahead”.  Instead I would use “Try to push by batch and …”
or something like that.

Note the typo: s/likelyhood/likelihood

Well, LGTM.

Cheers,
simon