From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: "Peter Grayson" <pete@jpgrayson.net>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH v3] Updated StGit patch detection in vcs_info
Date: Sat, 10 Dec 2022 13:31:43 +0000 [thread overview]
Message-ID: <798f47b2-3c38-4dac-bcfa-d022270ea57e@app.fastmail.com> (raw)
In-Reply-To: <e679937f-c54b-4f22-9a49-93985e8bd6a2@app.fastmail.com>
Peter Grayson wrote on Sat, 10 Dec 2022 12:55 +00:00:
> On Thu, Dec 8, 2022, at 8:37 PM, Daniel Shahaf wrote:
>> I'll go ahead and push that shortly (I just need this message to go
>> through so I have its X-Seq number).
>
> The updated patch seems to work perfectly for me. Good stuff. Thank
> you again for the collaboration on this!
Thanks for your reviews and patience! I'll definitely consider stg when
I next need patch stack management. (Though my distro only has stg 0.x ☹…)
In other news, I wonder: when there's an stg patch pushed and one does
a cherry-pick that conflicts, would it be desirable to show /both/ the cherry-pick
info and the stg stack info? That's already possible with vcs_info's
quilt support in add-on mode, and quilt and stg seems to be performing
similar functions here.
Cheers,
Daniel
next prev parent reply other threads:[~2022-12-10 13:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 20:43 [PATCH] Remove _stgit completion script 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 ` [PATCH] Remove _stgit completion script Peter Grayson
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 [this message]
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=798f47b2-3c38-4dac-bcfa-d022270ea57e@app.fastmail.com \
--to=d.s@daniel.shahaf.name \
--cc=pete@jpgrayson.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).