zsh-workers
 help / color / mirror / code / Atom feed
From: "Peter Grayson" <pete@jpgrayson.net>
To: "Daniel Shahaf" <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH] Remove _stgit completion script
Date: Mon, 31 Oct 2022 23:00:27 -0400	[thread overview]
Message-ID: <b4c60481-90af-4626-83b3-2f6ed35a5ca8@app.fastmail.com> (raw)
In-Reply-To: <20221031091933.GE27622@tarpaulin.shahaf.local2>

Thank you for taking the time to consider and merge this patch.

On Mon, Oct 31, 2022, at 5:19 AM, Daniel Shahaf wrote:
> Peter Grayson wrote on Tue, Oct 25, 2022 at 16:43:21 -0400:
>> The StGit project ships its own zsh completion script which is more
>> complete and up-to-date than those shipped with zsh.
>> 
>> https://github.com/stacked-git/stgit/blob/master/completion/stgit.zsh
>> 
>
> + I see that completion script gets updated in lockstep with stg(1)'s
>   argv parser.

Yes, maintaining that tight coupling between stg(1)'s command line
parsing and its comprehensive completion script has been important for
StGit development velocity. Although, maybe less velocity on the horizon
post StGit 2.0.

> + Given the two projects' release schedules it seems safe to assume that
>   by zsh's next release stg 2.0 will have been released as well, so most
>   users won't end up in a situation where they have neither _stgit nor
>   stgit.zsh.

StGit has been releasing its own zsh completion script since at least 1.0,
so there is not even a minor release timing concern.
 
> + No objections in a week.
>
> - _stgit and stgit.zsh are licenced differently.
>
> Being licenced under the same terms as zsh itself seems to be outweighed
> by not being regularly updated.  So, I've pushed this.  The last version
> is of course still available in our version control history.

If at any point we think it makes sense to migrate StGit's completion
script [back] to the zsh project, I would be happy to relicense.

> StGit is also used by vcs_info, here:
>
> https://github.com/zsh-users/zsh/blob/b76dcecfe3461aa9a9e29dffe2484f097611f9ff/Functions/VCS_Info/Backends/VCS_INFO_get_data_git#L187-L194
>
> (There doesn't seem to be StGit-specific code elsewhere in the file or
> in the sibling file VCS_INFO_detect_git.)
>
> Any chance that someone who uses both StGit and zsh could review that?
> That code is supposed to populate $gitmisc (and thus the %m expando)
> with information about pushed and not-yet-pushed patches.

Thanks for pointing this out--I didn't know about it. I've taken a look
and my conclusion is that the StGit patch state interrogation currently
found in VCS_INFO_get_data_git should also just simply be removed. I'll
send another patch shortly with the rationale in the commentary.

Cheers,
Pete


  parent reply	other threads:[~2022-11-01  3:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 20:43 Peter Grayson
2022-10-31  9:19 ` Daniel Shahaf
2022-10-31 10:13   ` StGit 2.0 and vcs_info (was: Re: [PATCH] Remove _stgit completion script) Daniel Shahaf
2022-11-01  3:00   ` Peter Grayson [this message]
2022-11-01  3:04     ` [PATCH] Remove StGit patch detection from vcs_info Peter Grayson
2022-11-11 11:49       ` Daniel Shahaf
2022-11-12 14:46         ` Peter Grayson
2022-11-12 15:42           ` [PATCH] Updated StGit patch detection in vcs_info Peter Grayson
2022-11-13  4:58             ` Daniel Shahaf
2022-11-16 20:45             ` [PATCH v2] " Peter Grayson
2022-12-08 14:52               ` [PATCH v3] " Peter Grayson
2022-12-08 22:06                 ` Daniel Shahaf
2022-12-08 22:08                   ` [PATCH] vcs_info git: Check the get-unapplied style as documented (was: [PATCH v3] Updated StGit patch detection in vcs_info) Daniel Shahaf
2022-12-09  0:59                   ` [PATCH v3] Updated StGit patch detection in vcs_info Peter Grayson
2022-12-09  1:37                     ` Daniel Shahaf
2022-12-10 12:55                       ` Peter Grayson
2022-12-10 13:31                         ` Daniel Shahaf
2022-11-13  4:30           ` [PATCH] Remove StGit patch detection from vcs_info Daniel Shahaf
2022-11-14  3:38             ` Peter Grayson
2022-11-14  5:17               ` Mikael Magnusson
2022-11-14 13:21                 ` Daniel Shahaf
2022-11-14 13:15               ` Daniel Shahaf
2022-11-16 19:38                 ` Peter Grayson

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=b4c60481-90af-4626-83b3-2f6ed35a5ca8@app.fastmail.com \
    --to=pete@jpgrayson.net \
    --cc=d.s@daniel.shahaf.name \
    --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).