Re: Reply for Auto parts

Dear Good day. This is Kevin from Future Mould and Plastic Technology Co.,Ltd. We supply plastic products for SUZUKI with high quality and competitive price. For instance, Dashboard panel, Steering wheel cover, Control Panel, Air conditioner outlet, Seat fitting, Cup holder, Gloves box, Rear

I want you to Distribute my funds to less priviledge if interested reply now

I am still waiting for your reply to my letter to you, Get back to me so that I can give you more details.

I want you to Distribute my funds to less priviledge if interested reply now

Reply-to: hm-treasury_off...@my.com

You are lucky to have £1,800,000.00GBP as your compensation grant. JC

Reply

Greeting, I contacted you last two weeks and I got no response. I mentioned about my late client that has the same surname with you. He deposited the sum of US$10.5 million dollars in one of the bank here in our country and they have asked me to provide a next of kin.Kindly show your interest to

URGENT REPLY NEEDED,REMINDER

Hello Dear, We are global financial provider, led by a dynamic Investment team. We are providing corporate and Personal Loan at 3% Interest Rate for a duration of 2 to 20 Years. We also pay 1% commission to brokers/person, who introduce project owners for finance or other opportunities. Contact

How are you doing today? Please read my email and reply me!!

Dear Sir/Madam, How are you doing today? My name is Billy Wilfred. I am California, United States of America. I am a broker of Project Financing Firm who has cutting edge and group capital fund, they can finance any lucrative project and help you to enhance your business plan. Are you in need

Important Notice...Reply Now

My wife and I won the Euro Millions Lottery of £53 Million British Pounds and we have voluntarily decided to donate €1,000,000EUR(One Million Euros) to 5 individuals randomly as part of our own charity project. To verify our lottery winnings,please see our interview by visiting the web page

Re: [PATCH] send-email: avoid duplicate In-Reply-To/References

il.perl >> +++ b/git-send-email.perl >> @@ -1642,10 +1642,15 @@ foreach my $t (@files) { >> elsif (/^Content-Transfer-Encoding: (.*)/i) { >> $xfer_encoding = $1 if not defined >> $xfer_encoding; >>

Re: [PATCH] send-email: avoid duplicate In-Reply-To/References

foreach my $t (@files) { > elsif (/^Content-Transfer-Encoding: (.*)/i) { > $xfer_encoding = $1 if not defined > $xfer_encoding; > } > + elsif (/^In-Reply-To: (.*)/i) { > +

[PATCH] send-email: avoid duplicate In-Reply-To/References

In case a patch already has In-Reply-To or References in the header (e.g. when the patch has been created with format-patch --thread) git-send-email should not add another pair of those headers. This is also not allowed according to RFC 5322 Section 3.6: https://tools.ietf.org/html/rfc5322#section

git send-mail sends with duplicate In-Reply-To/References header fields

Hi, Using git format-patch --thread + send-mail leads to In-Reply-To/References headers added twice (with the very same value). This is not allowed according to RFC 5322 Section 3.6: https://tools.ietf.org/html/rfc5322#section-3.6 Ideally probably git-format-patch should be smart about whether

Reply Immediately

Good Day My name is Benjamin Joseph, an accountant with C Bank UK, there is an opportunity in our bank that I would like us to talk about so we can join hands together to achieve it for our benefit. please get back to me for details. Thanks you Benjamin Joseph.

REPLY BACK PLEASE

this country. Please can you partner with me and receive the fund in your account while I come over there with my son for investment. If you agree, get back for more details and what will be your commission for the assistance. Call me please: +22967650091 I wait for your reply, Doris Markkoh

QUICK REPLY

Would you like to be part of our supply? Please respond back to my private email on: kuanwaich...@gmail.com

Reply

Dear Doron, I plead an indulgence if I have invaded your privacy by receiving this mail from me without prior permission. With due respect, I contact you purposely based on the similarities of names between you and my deceased client who was an oil servicing contractor with shell petroleum in West

Re: git-send-email: Support for Reply-To

Christian Ludwig writes: > this is the third iteration of this series. There was a request to > rebase the changes on the refactoring patch b6049542 ("send-email: > extract email-parsing code into a subroutine", 2017-12-15). This is > the result. Thanks. Let me Cc the

[PATCH v3 2/2] send-email: Support separate Reply-To address

In some projects contributions from groups are only accepted from a common group email address. But every individual may want to receive replies to her own personal address. That's what we have 'Reply-To' headers for in SMTP. So introduce an optional '--reply-to' command line option. This patch

git-send-email: Support for Reply-To

Hi, this is the third iteration of this series. There was a request to rebase the changes on the refactoring patch b6049542 ("send-email: extract email-parsing code into a subroutine", 2017-12-15). This is the result. The diffstat is the same compared to the last revision. It could be made

Reply

-- I was wondering if you got my previous Email to you regarding my proposal? best regards Email:robertwort...@outlook.com

Re: [PATCH v2 2/2] send-email: Support separate Reply-To address

On 17 January 2018 at 19:08, Christian Ludwig <chrissic...@googlemail.com> wrote: > In some projects contributions from groups are only accepted from a > common group email address. But every individual may want to recieve > replies to her own personal address. That's what

Re: [PATCH v2 2/2] send-email: Support separate Reply-To address

On Wed, Jan 17 2018, Christian Ludwig jotted: > +if (defined $reply_to) { > + $reply_to =~ s/^\s+|\s+$//g; > + ($reply_to) = expand_aliases($reply_to); > + $reply_to = sanitize_address($reply_to); > +} Just a note to other reviewers: I found it odd to call a function with one

Re: [PATCH v2 2/2] send-email: Support separate Reply-To address

Christian Ludwig <chrissic...@googlemail.com> writes: > In some projects contributions from groups are only accepted from a > common group email address. But every individual may want to recieve > replies to her own personal address. That's what we have 'Reply-To' > h

[PATCH v2 2/2] send-email: Support separate Reply-To address

In some projects contributions from groups are only accepted from a common group email address. But every individual may want to recieve replies to her own personal address. That's what we have 'Reply-To' headers for in SMTP. Introduce an optional '--reply-to' command line option. Unfortunately

Re: [PATCH] send-email: Support separate Reply-To address

> In some projects contributions from groups are only accepted from a > common group email address. But every individual may want to recieve > replies to her own personal address. That's what we have 'Reply-To' > headers for in SMTP. > > Introduce an optional '--reply-to' c

[PATCH] send-email: Support separate Reply-To address

In some projects contributions from groups are only accepted from a common group email address. But every individual may want to recieve replies to her own personal address. That's what we have 'Reply-To' headers for in SMTP. Introduce an optional '--reply-to' command line option. Unfortunately

Please reply immediately,

as your own son. Please reply immediately so that we can further discuss the details fast before anything happens to me. Yours Sincerely, Mrs. Sarah Faith.

Urgent reply is needed,

unclaimed as a result of non existing body.Provided you will put trust forward, let us share the deal if you are interested. Reply to this address;nodian.om...@gmail.com, Urgent reply is needed for more details. Regards, Mr, Nodian Omera,

Please reply, I have a genuine business to discuss with you.

reply. Sincerely Hussein Saleh

Reply

I have something very confidential and private to discuss with you

Re: [PATCH] patch reply

I just sent a patch to a new thread which is not what I wanted. However I already sent the same patch a few days ago: https://public-inbox.org/git/CAK7vU=2ePR3jQsgu=rxsmrxytaahqxc0sfrn5yozlzqzp2z...@mail.gmail.com/ 2017-10-17 6:01 GMT+02:00 Junio C Hamano : > Thais Diniz

Re: [PATCH] patch reply

Thais Diniz writes: > +Just to clarify I did not see Marius patch. > +Did see Marius' comment saying he would look it in the leftoverbits list, > +but since i didn't see any patch i thought i could work on it and did so > based on Stephan's comment > +(which i

[PATCH] patch reply

From: Thais Diniz Braz --- emailReply | 4 1 file changed, 4 insertions(+) create mode 100644 emailReply diff --git a/emailReply b/emailReply new file mode 100644 index 0..2d591b55b --- /dev/null +++ b/emailReply @@ -0,0 +1,4 @@ +Just to clarify I did

I am waiting for your Reply

sharing ratio will be 50% for me and 40% for you, While 10% will be for the necessary expenses that might occur along the line. I expect your reply. Sincerely, Mr.Patrick Joseph.

Re: Reply Urgent

Hello, How are you doing? We have an inheritance of a deceased client with your surname. Contact Mr Andrew Bailey by this email address: ands...@europe.com with your full names for further information's. Thanks for your understanding. Melissa. -- Correo

REPLY NOW:

Did you receive my previous message about my donation to you? for philanthropic and humanitarian work for all of mankind who are in great need among your friends, family and people around you. REPLY FOR MORE DETAILS. Regards Mrs Mavis Wanczyk.

IMMEDIATE REPLY NEEDED.

Dear, My name is Mr Alaine Kamba, I am the Bill and Exchange (assistant) Manager of Bank of Africa Ouagadougou, Burkina Faso. In my department I discovered an abandoned sum of eighteen million three hundred thousand United State of American dollars (18.3MILLION USA DOLLARS) in an account that

I Am Mrs Juliana Timothy,i have important thing to discus with you Wating For Your Reply Thanks

I Have A Donation For You

URGENT REPLY FOR MORE DETAILS.

of your reply on your expression of Interest I will give you full details, on how the business will be executed I am open for negotiation. Thanks for your anticipated cooperation. Note you might receive this message in your inbox or spam or junk folder, depends on your web host or server network

URGENT REPLY FOR MORE DETAILS.

of your reply on your expression of Interest I will give you full details, on how the business will be executed I am open for negotiation. Thanks for your anticipated cooperation. Note you might receive this message in your inbox or spam or junk folder, depends on your web host or server network

URGENT REPLY FOR MORE DETAILS.

receipt of your reply on your expression of Interest I will give you full details, on how the business will be executed I am open for negotiation. Thanks for your anticipated cooperation. Note you might receive this message in your inbox or spam or junk folder, depends on your web host or server

Urgent reply needed,

unclaimed as a result of non existing body.Provided you will put trust forward, let us share the deal if you are interested. Urgent reply is needed for more details.Reply to: amuji...@gmail.com, Regards, Mr.Alimuji Gabratai,

Re: My Second Email to You, Pls Reply Me

Hello Dear, How are you doing? I hope you are doing well. I am writing as I have written to you previously without any response from you. I hope all is well with you.I will appreciate if you will acknowledge your receipt of this mail. Thank you and have a good day. Miss Naya Please Write Me

Reply me back!!

I have been trying to reach you

this is urgent reply.

will not like you to joke with it ok, MY name is Mr. zaki ibrahim i am working in ADB bank I have ($17.4million Dollars) to transfer to your country and if you are interested get back to me immediately for more details.and i we give you 40% for you and 60% for me ok. Please note; reply me through

Re: My Second Email to You, Pls Reply Me Soon

Hello Dear, How are you doing? I hope you are doing well. I am writing as I have written to you previously without any response from you. I hope all is well with you.I will appreciate if you will acknowledge your receipt of this mail. Thank you and have a good day. Mrs Fatma. Please Write Me

KINDLY REPLY URGENTLY

Dear Friend I am contacting you on a business deal of $9,500,000.00 Million United States Dollars, ready for transfer into your own personal account and if we make this claim, we will share it on the ratio of 50% / 50% basis, I would like to assure you that it be 100% risk free and it will be

Please i need your urgent and sincere reply

information on how the fund will be transferred to your bank account. I am waiting for your reply and my private email address is caronglori...@yahoo.com Thank you, Mrs Gloria

Re: [PATCH v4 1/3] usability: don't ask questions if no reply is required

Johannes Sixt writes: > Am 13.05.2017 um 00:36 schrieb Junio C Hamano: >> Thanks, all three patches look good. Will queue. >> >> Let's merge them to 'next' soonish and eventually down to 'master' >> and 'maint'. > > The patches change translated strings. You should probably wait

Re: [PATCH v4 1/3] usability: don't ask questions if no reply is required

Am 13.05.2017 um 00:36 schrieb Junio C Hamano: Thanks, all three patches look good. Will queue. Let's merge them to 'next' soonish and eventually down to 'master' and 'maint'. The patches change translated strings. You should probably wait for an update of their translations before you

Re: [PATCH v4 1/3] usability: don't ask questions if no reply is required

Thanks, all three patches look good. Will queue. Let's merge them to 'next' soonish and eventually down to 'master' and 'maint'. Thanks.

[PATCH v4 1/3] usability: don't ask questions if no reply is required

ates which are close to the unexisting command. E.g Git prints the following: git: 'stahs' is not a git command. See 'git --help'. Did you mean this? stash and then exits. The problem with this hint is that it is not formally indicated as an hint and the user is in fact encourage

[PATCH v3 1/3] usability: don't ask questions if no reply is required

ates which are close to the unexisting command. E.g Git prints the following: git: 'stahs' is not a git command. See 'git --help'. Did you mean this? stash and then exits. The problem with this hint is that it is not formally indicated as an hint and the user is in fact encourage

Re: [PATCH v2 1/3] usability: don't ask questions if no reply is required

On Thu, May 11, 2017 at 12:28 PM, Konstantin Khomoutov wrote: > On Thu, May 11, 2017 at 10:10:05AM +, Kerry, Richard wrote: > > [...] >> > > @@ -1940,7 +1940,7 @@ static void am_resolve(struct am_state *state) >> > > >> > > if (unmerged_cache()) { >> > >

Re: [PATCH v2 1/3] usability: don't ask questions if no reply is required

On Thu, May 11, 2017 at 10:10:05AM +, Kerry, Richard wrote: [...] > > > @@ -1940,7 +1940,7 @@ static void am_resolve(struct am_state *state) > > > > > > if (unmerged_cache()) { > > > printf_ln(_("You still have unmerged paths in your index.\n" > > > - "Did

RE: [PATCH v2 1/3] usability: don't ask questions if no reply is required

g; rashmipa...@gmail.com > Subject: Re: [PATCH v2 1/3] usability: don't ask questions if no reply is > required > > Jean-Noel Avila <jn.av...@free.fr> writes: > > > diff --git a/builtin/am.c b/builtin/am.c index a95dd8b4e..f5afa438d > > 100644 > > --- a/builtin/a

Re: [PATCH v2 1/3] usability: don't ask questions if no reply is required

Jean-Noel Avila writes: > diff --git a/builtin/am.c b/builtin/am.c > index a95dd8b4e..f5afa438d 100644 > --- a/builtin/am.c > +++ b/builtin/am.c > @@ -1312,7 +1312,7 @@ static int parse_mail(struct am_state *state, const > char *mail) > } > > if

Re: [PATCH v2 1/3] usability: don't ask questions if no reply is required

sender does not warrant that >> this transmission is virus-free and will not be liable for any damages >> resulting from any virus transmitted. >> >> >> From: Ævar Arnfjörð Bjarmason [ava...@gmail.com] >> Sent: 04 May 20

Re: [PATCH v2 1/3] usability: don't ask questions if no reply is required

from any virus transmitted. > > > From: Ævar Arnfjörð Bjarmason [ava...@gmail.com] > Sent: 04 May 2017 10:09 > To: Kerry, Richard > Cc: git@vger.kernel.org > Subject: Re: [PATCH v2 1/3] usability: don't ask questions if no reply is >

RE: [PATCH v2 1/3] usability: don't ask questions if no reply is required

git@vger.kernel.org Subject: Re: [PATCH v2 1/3] usability: don't ask questions if no reply is required On Thu, May 4, 2017 at 10:52 AM, Kerry, Richard <richard.ke...@atos.net> wrote: > > May I suggest that " The most approaching commands" doesn't make much sense > as English

Re: [PATCH v2 1/3] usability: don't ask questions if no reply is required

Le jeudi 4 mai 2017, 08:52:43 CEST Kerry, Richard a écrit : > > May I suggest that " The most approaching commands" doesn't make much sense > as English (I don't think a command can "approach"). > Perhaps it should be " The most appropriate commands". > > > Regards, > Richard. > Thank you

Re: [PATCH v2 1/3] usability: don't ask questions if no reply is required

, Stadium House, Wood Lane, London, W12 7TA > richard.ke...@atos.net > > > > > -Original Message- > From: git-ow...@vger.kernel.org [mailto:git-ow...@vger.kernel.org] On Behalf > Of Jean-Noel Avila > Sent: Wednesday, May 03, 2017 10:07 PM > To: git@vger.kernel.org > Cc: rash

RE: [PATCH v2 1/3] usability: don't ask questions if no reply is required

: Wednesday, May 03, 2017 10:07 PM To: git@vger.kernel.org Cc: rashmipa...@gmail.com; Jean-Noel Avila <jn.av...@free.fr> Subject: [PATCH v2 1/3] usability: don't ask questions if no reply is required There has been a bug report by a corporate user that stated that "spelling mistake o

[PATCH v2 1/3] usability: don't ask questions if no reply is required

ates which are close to the unexisting command. E.g Git prints the following: git: 'stahs' is not a git command. See 'git --help'. Did you mean this? stash and then exits. The problem with this hint is that it is not formally indicated as an hint and the user is in fact encourage

Re: [PATCH 1/4] usability: don't ask questions if no reply is required

stand the patch here so they don't have to. Ok. Will include more context in the commit message and just provide the BT as an additional link. > > > the user was disconcerted by the question asked by the program not > > requiring a reply from the user. To improve the general usabili

Re: [PATCH 1/4] usability: don't ask questions if no reply is required

ation the reader needs to > understand the patch here so they don't have to. > >> the user was disconcerted by the question asked by the program not >> requiring a reply from the user. To improve the general usability of >> the Git suite, The following rule was applied: &g

Re: [PATCH 1/4] usability: don't ask questions if no reply is required

one place. In other words, instead of asking the reader to read the bug report, please include pertinent information the reader needs to understand the patch here so they don't have to. > the user was disconcerted by the question asked by the program not > requiring a reply from the user. To impr

[PATCH 1/4] usability: don't ask questions if no reply is required

As described in the bug report at https://github.com/git/git-scm.com/issues/999 the user was disconcerted by the question asked by the program not requiring a reply from the user. To improve the general usability of the Git suite, The following rule was applied: if the sentence * appears

Please reply ASAP (For Alex)

for our mutual benefit. For your assistance as the account owner we shall share the funds equally. If interested contact me through email for more details. My email address is: mralexlee7...@gmail.com Please reply ASAP. Mr. Alex Lee.

Re:GOOD DAY AND URGENT REPLY.

MY name is Mr. ahmed zongo i am working in ADB bank I have ($17.4million Dollars) to transfer to your country and if you are interested get back to me immediately for more details.and i we give 40% for you and 60% for me ok. Please note; reply me through this email (zongoahmed...@gmail.com

Re: [RFC] send-email: avoid duplicate In-Reply-To and References headers

Eric Wong <e...@80x24.org> writes: > Junio C Hamano <gits...@pobox.com> wrote: >> >> I think it is sensibleto give priority to the --in-reply-to option >> given from the command line over the in-file one. I am not sure if >> we want to drop reference

Re: [RFC] send-email: avoid duplicate In-Reply-To and References headers

Junio C Hamano <gits...@pobox.com> wrote: > Eric Wong <e...@80x24.org> writes: > > When parsing an mbox, it is possible to get existing In-Reply-To > > and References headers blindly appended into the headers of > > message we generate. This is probably the wr

Re: [RFC] send-email: avoid duplicate In-Reply-To and References headers

Eric Wong <e...@80x24.org> writes: > When parsing an mbox, it is possible to get existing In-Reply-To > and References headers blindly appended into the headers of > message we generate. This is probably the wrong thing to do > and we should prioritize what was given i

[RFC] send-email: avoid duplicate In-Reply-To and References headers

When parsing an mbox, it is possible to get existing In-Reply-To and References headers blindly appended into the headers of message we generate. This is probably the wrong thing to do and we should prioritize what was given in the command-line, cover letter, and previously-sent messages. One

REPLY NOW

We have an inheritance of a deceased client with your surname. Kindly contact Andrew Bailey via email with your full Names and address. ( baanidle...@hotmail.com )for more info. -- Correo Corporativo Hospital Universitario del Valle E.S.E

Please reply me

My dear friend, I am Mrs Rebecca Taylor from Kuwait married to Late Mr. Alfred Taylor from Ivory Coast West Africa, of paroisse saint sebastien Church. I and My late husband has done numerous charity service within and outside our region since 1981. We have been doing our best to promote

I will be waiting for your reply

Hello, My name is Chan Chak a bank manager with an investment bank, I have a business deal of mutual benefit that involve transfer of large sum of money. Get back to me through my private email:- chanch...@gmail.com for more details if you are interested. CHAN CHAK -- To unsubscribe from this

Re: [PATCH v4 5/6] send-email: --in-reply-to= populate header fields

il.txt @@ -84,13 +84,16 @@ See the CONFIGURATION section for 'sendemail.multiEdit'. the value of GIT_AUTHOR_IDENT, or GIT_COMMITTER_IDENT if that is not set, as returned by "git var -l". ---in-reply-to=:: +--in-reply-to=<Message-Id|email_file>:: Make the first

Re: [PATCH v4 5/6] send-email: --in-reply-to= populate header fields

quot;; instead? That's way cleaner, thanks! By the way, this is a good example why your "unfold" implementation in 4/6 is unwieldy for the caller. Imagine a rather long subject that is folded, i.e. To: Samuel Subject: Help! I am having a trouble running gi

Re: [PATCH v4 5/6] send-email: --in-reply-to= populate header fields

@@ See the CONFIGURATION section for 'sendemail.multiEdit'. > the value of GIT_AUTHOR_IDENT, or GIT_COMMITTER_IDENT if that is not > set, as returned by "git var -l". > > ---in-reply-to=:: > +--in-reply-to=<Message-Id|email_file>:: > Make t

Re: [PATCH v4 5/6] send-email: --in-reply-to= populate header fields

Samuel GROOT writes: > +if ($initial_reply_to && -f $initial_reply_to) { > + my $error = validate_patch($initial_reply_to); This call is wrong, isn't it? You are not going to send out the message you are responding to (the message may not even be a patch),

[PATCH v4 5/6] send-email: --in-reply-to= populate header fields

Take an email message file, parse it and fill the "From", "To", "Cc", "In-reply-to", "References" fields appropriately. If `--compose` option is set, it will also fill the subject field with `Re: ['s subject]` in the introductory message.

[PATCH v3 5/6] send-email: --in-reply-to= populates the fields

Take an email message file, parse it and fill the "From", "To", "Cc", "In-reply-to", "References" fields appropriately. If `--compose` option is set, it will also fill the subject field with `Re: ['s subject]` in the introductory message.

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

Samuel GROOT <samuel.gr...@grenoble-inp.org> writes: > On 05/25/2016 08:31 PM, Matthieu Moy wrote: >> So, a possible UI would be: >> >> git send-email --in-reply-to= => just set In-Reply-To: field. >> >> git send-email --in-reply-to= => set I

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

On 05/25/2016 08:31 PM, Matthieu Moy wrote: So, a possible UI would be: git send-email --in-reply-to= => just set In-Reply-To: field. git send-email --in-reply-to= => set In-Reply-To, To and Cc. git send-email --in-reply-to= --cite => in addition, add the body of the messa

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

Junio C Hamano <gits...@pobox.com> writes: > Matthieu Moy <matthieu@grenoble-inp.fr> writes: > >> This should work, but sounds like too much of overloading of >> --in-reply-to IMHO: if given a message id, it would only add a reference >> to this message-id

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

Matthieu Moy <matthieu@grenoble-inp.fr> writes: > This should work, but sounds like too much of overloading of > --in-reply-to IMHO: if given a message id, it would only add a reference > to this message-id, but if given a file, it would also modify the To: > and Cc: list

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

Junio C Hamano <gits...@pobox.com> writes: > I wonder if we can safely repurpose existing --in-reply-to option? In theory, obviously no as there can be a file with this name _and_ it can be a valid message-id. In practice, it is clearly unlikely. The only use-case I can think of where b

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

Matthieu Moy <matthieu@grenoble-inp.fr> writes: > Actually, I'm not sure what the ideal behavior should be. Perhaps it's > better to distinguish 1) and 2) above, and have two options > --reply-to-email= doing 1), and --quote doing 2), implying > --compose and requiring --

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

ould be. Perhaps it's better to distinguish 1) and 2) above, and have two options --reply-to-email= doing 1), and --quote doing 2), implying --compose and requiring --reply-to-email. That would be more flexible, but that would require two new options, and I also like to keep things simple. In any

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

On 05/25/16 00:30, Aaron Schrab wrote: > At 14:49 +0200 24 May 2016, Matthieu Moy > wrote: >> Samuel GROOT writes: >> >>> What kind of help text would you want to see? >>> >>> Maybe something like this: >>> >>> GIT: Quoted message

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

On 05/23/2016 10:00 PM, Matthieu Moy wrote: I don't think this is right: I often reply to an email with a single patch, for which it would clearly be overkill to have a cover-letter. Yes indeed, we are working on inserting the quoted message body in the patch's "below-triple-dash&quo

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

At 14:49 +0200 24 May 2016, Matthieu Moy wrote: Samuel GROOT writes: What kind of help text would you want to see? Maybe something like this: GIT: Quoted message body below. GIT: Feel free to trim down the quoted text GIT:

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

Samuel GROOT wrote: > On 05/23/2016 09:55 PM, Eric Wong wrote: > >Cool! There should probably be some help text to encourage > >trimming down the quoted text to only relevant portions. > > What kind of help text would you want to see? > > Maybe something like

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

Samuel GROOT writes: > On 05/23/2016 09:55 PM, Eric Wong wrote: >> Tom Russello wrote: >>> This new option takes an email message file, parses it, fills the "To", >>> "Subject" and "Cc" fields appropriately and quote the message. >>>

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

On 05/23/2016 09:55 PM, Eric Wong wrote: Tom Russello wrote: This new option takes an email message file, parses it, fills the "To", "Subject" and "Cc" fields appropriately and quote the message. This option involves the `--compose` mode to edit the cover

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

UAs prefix unconditionally with "> ". I had the same question, but at least my mailer (Gnus) has the same special-case it seems. Thunderbird behaves the same way, so we decided to mimic that behavior. It is specified neither in RFC 2822 [1] nor in RFC 5322 [2]. When we write an emai

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

Eric Wong writes: > Tom Russello wrote: > >> +#Message body >> +while (<$fh>) { >> +#for files containing crlf line endings >> +$_=~ s/\r//g; >> +my $space=""; >> +if (/^[^>]/) { >> +

Re: [RFC-PATCH 1/2] send-email: new option to quote an email and reply to

Tom Russello <tom.russe...@grenoble-inp.org> writes: > This option involves the `--compose` mode to edit the cover letter quoting the s/involves/implies/ ? I don't think this is right: I often reply to an email with a single patch, for which it would clearly be overkill to have a cov

  1   2   >