From: "David Kågedal" <davidk@lysator.liu.se>
To: git <git@vger.kernel.org>
Subject: Re: [StGit PATCH 1/6] Split git.merge into two functions
Date: Mon, 20 Aug 2007 10:55:28 +0200 [thread overview]
Message-ID: <87odh2d1q7.fsf@morpheus.local> (raw)
In-Reply-To: <1187597523433-git-send-email-davidk@lysator.liu.se> (David Kågedal's message of "Mon, 20 Aug 2007 10:11:58 +0200")
David Kågedal <davidk@lysator.liu.se> writes:
> From: David KÃ¥gedal <davidk@lysator.liu.se>
It seems that git-send-email didn't like me for some reason. Double
UTF-8 encoding is not very pretty.
I also got a number of these when running it:
W: unable to extract a valid address from: David KÃ¥gedal <davidk@lysator.liu.se>
W: unable to extract a valid address from: David KÃ¥gedal <davidk@lysator.liu.se>
(the above was written in my latin1 xterm, so it wasn't double-encoded
there)
Is there a way to make send-email not add a "From:" header to the body
of the message? The header already had the correct "From:" line.
--
David Kågedal
next prev parent reply other threads:[~2007-08-20 8:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 8:11 [StGit PATCH 0/6] Use git conflict handling on push David Kågedal
2007-08-20 8:11 ` [StGit PATCH 1/6] Split git.merge into two functions David Kågedal
2007-08-20 8:11 ` [StGit PATCH 2/6] Don't try to merge files that merge-recursive already merged David Kågedal
2007-08-20 8:12 ` [StGit PATCH 3/6] Don't touch state after conflict in push David Kågedal
2007-08-20 8:12 ` [StGit PATCH 4/6] Added a test case to check what happens when push finds a conflict David Kågedal
2007-08-20 8:12 ` [StGit PATCH 5/6] Simplify merge_recursive David Kågedal
2007-08-20 8:12 ` [StGit PATCH 6/6] Use the output from merge-recursive to list conflicts David Kågedal
2007-08-22 9:21 ` [StGit PATCH 2/6] Don't try to merge files that merge-recursive already merged Karl Hasselström
2007-08-22 9:37 ` David Kågedal
2007-08-22 9:44 ` Karl Hasselström
2007-08-22 9:59 ` Karl Hasselström
2007-08-22 10:29 ` [StGIT PATCH] Leave working dir and index alone after failed (conflicting) push Karl Hasselström
2007-08-20 8:55 ` David Kågedal [this message]
2007-08-20 23:52 ` [StGit PATCH 1/6] Split git.merge into two functions Junio C Hamano
2007-08-21 19:35 ` Uwe Kleine-König
2007-08-22 10:04 ` Junio C Hamano
2007-08-22 9:17 ` [StGit PATCH 0/6] Use git conflict handling on push Karl Hasselström
2007-08-23 14:54 ` Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2007-08-26 20:42 [StGIT PATCH 0/6] David's conflict series using my subprocess stuff Karl Hasselström
2007-08-26 20:42 ` [StGIT PATCH 1/6] Split git.merge into two functions Karl Hasselström
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=87odh2d1q7.fsf@morpheus.local \
--to=davidk@lysator.liu.se \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.