zsh-workers
 help / color / mirror / code / Atom feed
From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Gregory Seidman" <gsslist+zshdev@anthropohedron.net>
Cc: zsh-workers@zsh.org
Subject: Re: Extending zsh hooks
Date: Tue, 07 Nov 2023 21:35:30 -0500	[thread overview]
Message-ID: <509022a0-b851-4203-bf83-7d6e26660b82@app.fastmail.com> (raw)
In-Reply-To: <ZUrIw5vMVT7Yjpvo@peterbilt.lan>

On Tue, Nov 7, 2023, at 6:31 PM, Gregory Seidman wrote:
> While I've found https://sourceforge.net/p/zsh/code/ci/master/tree/ I am a
> lot more familiar with contributing to FLOSS on GitHub by forking and a PR.
> Does it work the same way on SourceForge? (Also, my SourceForge account
> seems to have gone away, maybe because I haven't used it in over a decade,
> but I can make a new one.)

The usual process is to propose changes on this list and include
any patches inline or as an attachment.  You can find many examples
in the archive (e.g., <https://www.zsh.org/mla/workers/2023/>).

-- 
vq


  reply	other threads:[~2023-11-08  2:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 23:31 Gregory Seidman
2023-11-08  2:35 ` Lawrence Velázquez [this message]
2023-11-08 19:16   ` PATCH: custom zsh hooks (was Re: Extending zsh hooks) Gregory Seidman
2023-11-09  5:13     ` Bart Schaefer
2023-11-09  4:09   ` Extending zsh hooks Bart Schaefer

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

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

  git send-email \
    --in-reply-to=509022a0-b851-4203-bf83-7d6e26660b82@app.fastmail.com \
    --to=larryv@zsh.org \
    --cc=gsslist+zshdev@anthropohedron.net \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).