-
Notifications
You must be signed in to change notification settings - Fork 284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patch export #318
Comments
I think at the moment the outputs of |
Looks like in Are extensions a thing with |
@nemith Extensions are also a thing in Sapling (see https://github.com/facebook/sapling/tree/main/eden/scm/edenscm/ext ) I'm not sure how compatible would that extension be with Sapling, however. |
Is changing the output of I'm assuming it's ok since We'd also need some sort of |
Hello @zzl0 , |
@VishalGawade1 I don’t believe anyone is actively working on it. Thank you for your interest—please feel free to take it on! |
Thanks a lot! I'll update you soon :) |
Hello @zzl0 ,
("", "email", False, _("format export in email style")),
Let me know if this approach works for you, and I can go ahead with raising a PR. Or, if there’s anything else you’d like me to adjust |
Hello @zzl0 , |
Go ahead :) |
Hello @williewillus , |
@VishalGawade1 sorry for the late reply, how do you think about this comment? |
It would be nice if we had the ability to export commits under the Git email .patch (example: https://patch-diff.githubusercontent.com/raw/facebook/sapling/pull/287.patch)
I use the mailing list patch workflow for some personal projects and would love to use sl to manage the repo, but exporting diffs to mail is a bit difficult right now.
sl export
exists, but it's descended from hg export and does not have all the information the Git patch format does (From lines, date, Subject lines, diffstat, unified file diffs)The text was updated successfully, but these errors were encountered: