From: zimoun <email@example.com> To: Kyle Meyer <firstname.lastname@example.org>, email@example.com Subject: Re: [PATCH 0/6] Support applying patches in a new worktree Date: Sun, 15 Nov 2020 14:31:59 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Hi Kyle, Thank you. On Sun, 15 Nov 2020 at 01:15, Kyle Meyer <firstname.lastname@example.org> wrote: > With patch 4, something like that should be possible with both piem-am > and piem-b4-am-from-mid. When the new piem-am-create-worktree option > is set to a non-nil value, the caller will be prompted for a directory > where the new worktree should be created. > > Patch 5 makes it possible to trigger this in a one-off fashion with a > prefix argument because, while I don't want this behavior most of the > time, I could see myself using it every now and then. That’s awesome! I am going to test all that. I am currently running out of time because lockdown=extra-work+weird-feelings and the coming online Guix Days (and release v1.2 even if Ludo did everything). Well, I will report you my feedback soon and will try to add a section to the Guix Cookbook; anyhow, I have to add one after my experience as Outreach mentor. :-) Cheers, simon
next prev parent reply other threads:[~2020-11-15 13:34 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-15 6:15 Kyle Meyer 2020-11-15 6:15 ` [PATCH 1/6] piem-am: Rephrase CODEREPO description Kyle Meyer 2020-11-15 6:15 ` [PATCH 2/6] piem-am: Store "empty string" branch check Kyle Meyer 2020-11-15 6:15 ` [PATCH 3/6] am: Support creating a new worktree Kyle Meyer 2020-11-15 6:15 ` [PATCH 4/6] am: Add option to configure how worktree is read Kyle Meyer 2020-11-15 6:15 ` [PATCH 5/6] am: Allow flipping worktree creation with prefix argument Kyle Meyer 2020-11-15 6:15 ` [PATCH 6/6] manual: Document worktree-related options Kyle Meyer 2020-11-15 13:31 ` zimoun [this message] 2020-11-15 19:26 ` [PATCH 0/6] Support applying patches in a new worktree Kyle Meyer 2020-11-15 22:32 ` Kyle Meyer 2020-11-15 23:47 ` zimoun
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://git.kyleam.com/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 0/6] Support applying patches in a new worktree' \ /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
Code repositories for project(s) associated with this inbox: https://git.kyleam.com/piem/ 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).