unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Dmitry Alexandrov <dag@gnui.org>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: pull requests for guile
Date: Mon, 08 May 2023 14:32:02 +0300	[thread overview]
Message-ID: <mt2f83f1.dag@gnui.org> (raw)
In-Reply-To: <781a3ed7-6fcd-b502-a03b-6ae63279be75@gmail.com> (Matt Wette's message of "Sat, 6 May 2023 09:21:33 -0700")

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

Matt Wette <matt.wette@gmail.com> wrote:
> Does the savannah git repo support `git-request-pull'?

To the best of my knowledge, no any server-side support is required for that.

Git is intentionally designed to avoid any reliance on servers as much as possible.

> And if so, would that make getting patches in more efficient?

I would like to double that question with no any particular connection to Guile.

I fully understand why many developers generally refuse to review freeform pull requests and ask to send patches via their favourite integrated platform (such as gitlab or github) — anyone can evaluate extra features they provide.

Yet, I fail to get why so many teams insist that patches must be submitted as per git-format-patch.

Evidently, this is because they habitually rely on some tooling, that expects patchsets in that format.  But what is that tooling?

The only thing the I am aware of is git-am, which provides... nothing (?) over a simple pull request.

There must be some bits of hidden knowledge, passed from generation to generation of maintainers of venerable bazaar-style projects. ;-)

So, I would be glad if Guile / Guix / etc patch-reviewers shared some details about their workflow.

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

  reply	other threads:[~2023-05-08 11:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-06 16:21 pull requests for guile Matt Wette
2023-05-08 11:32 ` Dmitry Alexandrov [this message]
2023-05-08 16:27   ` Josselin Poiret
2023-05-08 21:03     ` Dr. Arne Babenhauserheide
2023-05-08 17:03 ` Arsen Arsenović

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=mt2f83f1.dag@gnui.org \
    --to=dag@gnui.org \
    --cc=guile-devel@gnu.org \
    --cc=matt.wette@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).