From: "Vít Ondruch" <vondruch@redhat.com>
To: Junio C Hamano <gitster@pobox.com>,
Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: Is there a way to get the "format-patch" formatted file name?
Date: Fri, 1 Sep 2023 18:37:45 +0200 [thread overview]
Message-ID: <36fcd3ae-19c8-23c6-fcb0-a20230ee4622@redhat.com> (raw)
In-Reply-To: <xmqqwmx9ritx.fsf@gitster.g>
[-- Attachment #1.1: Type: text/plain, Size: 1731 bytes --]
Dne 01. 09. 23 v 17:53 Junio C Hamano napsal(a):
> Oswald Buddenhagen <oswald.buddenhagen@gmx.de> writes:
>
>> but i wouldn't be opposed to for example git-mailinfo learning to
>> understand the --pretty argument, if the implementation doesn't turn
>> out to be completely out of proportion.
> Excellent suggestion. I agree that 'mailinfo' would be the closest
> place we have for such a new feature. It's "info" output (i.e. what
> comes out to the standard output of the command) is designed to be
> extensible, and I vaguely recall that we indeed have added new
> field(s) during its lifetime with existing users already.
>
> We can just invent a new label (e.g. "Filesystem-safe-subject:"),
> pass the subject string to pretty.c:format_sanitized_subject() and
> emit the result next to the existing "Subject:" with that label, and
> we can even do so unconditionally without breaking anybody.
'mailinfo' is new to me. I am not really sure what is the proper use of
this tool, but it sound as a neat idea. I could certainly extract the
string from the 'mailinfo' output and it works just above the .patch
file, which is great.
>
>
> Having it in 'mailinfo' may still not be a good solution to the
> issue, given that Vit says
>
>>> But I typically don't have a Git.
> though.
Well, this should have been "I typically don't have a Git *repository*",
because I certainly have a Git. Otherwise I would not ask for this
functionality.
Just to explain, I would need to expand the sources, which I typically
don't do. I'd need initialize the repository and commit everything,
apply the patch, etc. In that case, I'd rater keep manually changing the
patch names :)
Vít
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2023-09-01 16:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 9:49 Is there a way to get the "format-patch" formatted file name? Vít Ondruch
2023-08-31 11:04 ` Oswald Buddenhagen
2023-08-31 12:13 ` Vít Ondruch
2023-08-31 12:46 ` Oswald Buddenhagen
2023-08-31 17:19 ` Junio C Hamano
2023-09-01 8:56 ` Vít Ondruch
2023-09-01 11:00 ` Oswald Buddenhagen
2023-09-01 15:53 ` Junio C Hamano
2023-09-01 16:04 ` Junio C Hamano
2023-09-01 16:37 ` Vít Ondruch [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36fcd3ae-19c8-23c6-fcb0-a20230ee4622@redhat.com \
--to=vondruch@redhat.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=oswald.buddenhagen@gmx.de \
/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.
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).