From: Xinglu Chen <firstname.lastname@example.org> To: Kyle Meyer <email@example.com> Cc: firstname.lastname@example.org Subject: Re: Merge projects? Date: Sun, 17 Jan 2021 11:48:03 +0100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Sat, Jan 16 2021, Kyle Meyer wrote: > The second feature (sending patches) isn't something I had really > imagined supporting in piem. That's not because I don't think people > would find it useful; based on discussions on Magit's issue tracker > about git-send-email , I believe there's a good amount of interest > in such functionality. However, I think what particular workflow will > work for a person is likely to vary a lot and depend on several > factors, to the point where a large number of users will end up > creating their own tailored process . My current thinking is that > it makes sense to have dedicated packages that add support for > specific workflows, and that this functionality is orthogonal to > functionality for applying patches. Good point, it seems like everyone has a slightly different workflow when using git-format-patch and git-send-email. > So, I don't know. I'm not sure piem is a good home for "send patches" > functionality. Yeah, it is probably better for something like Magit or VC to offer this functionality. > My primary interest with piem is public-inbox, and there's some very > exciting work upstream on a local client  that I plan to support. This looks exciting, I would love to see an interface for lei, this would make it much faster than using Gnus over NNTP. > To use my odd workflow as an example: I prefer to call > git-format-patch and track the cover letter and patches in a > dedicated branch. For rerolls of a series, I overwrite the branch, > and use its reflog to carry over details I want from the previous > iterations (e.g., bits of the cover letter, remarks after the commit > message). Then I just send it out with a plain git-send-email, > sometimes with the --in-reply-to and --cc's coming from > notmuch-show-stash-git-send-email. Thanks for explaining your workflow and pointing out `notmuch-show-stash-git-send-email`, I will definitely make use of it in the future. -- Xinglu Chen
prev parent reply other threads:[~2021-01-17 10:48 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-16 10:11 Xinglu Chen 2021-01-16 21:26 ` Kyle Meyer 2021-01-17 10:48 ` Xinglu Chen [this message]
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: Merge projects?' \ /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).