From: Frank Terbeck <ft@bewatermyfriend.org>
To: Richard Hartmann <richih.mailinglist@gmail.com>
Cc: zsh workers <zsh-workers@zsh.org>
Subject: Re: New vcsh completion
Date: Wed, 24 Jul 2013 16:47:16 +0200 [thread overview]
Message-ID: <874nbkhv63.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <CAD77+gQ8xZtzAtYsFqHM2pevAx4Tu-npX8ew_BNdNsPd+cnozQ@mail.gmail.com> (Richard Hartmann's message of "Wed, 24 Jul 2013 16:16:53 +0200")
Richard Hartmann wrote:
> I would like to update the completion for vcsh. I do have commit
> access (thanks to my triaging work in the past), but I don't want to
> step onto anyone's toes and simply have been inactive/passive on this
> list for too long to _know_.
>
> Should I
>
> * just commit
> * send patch to here
> * send file to here
You can commit the change yourself, if you have commit access.
However, every change needs a ChangeLog entry. You will also have to
send the patch through the mailing list, because every change need to be
referenced by the number from the X-Seq: header the mailing list
software adds. That's why the commit messages look like this:
31465: fix basic completion and globbing uses of disabled patterns
With the corresponding ChangeLog entry looking like this:
[snip]
2013-06-13 Peter Stephenson <p.w.stephenson@ntlworld.com>
󠇨* 31465: Completion/compinit, Src/glob.c, Src/pattern.c: fix
basic completion and globbing use of pattern disables.
[snap]
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
next prev parent reply other threads:[~2013-07-24 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 14:16 Richard Hartmann
2013-07-24 14:27 ` Peter Stephenson
2013-07-24 14:27 ` Bart Schaefer
2013-07-24 14:47 ` Frank Terbeck [this message]
2013-07-24 14:51 ` [PATCH] Completion/Unix/Command/_vcsh: Update Richard Hartmann
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=874nbkhv63.fsf@ft.bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=richih.mailinglist@gmail.com \
--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).