From: Daniele Segato <daniele.segato@gmail.com>
To: Stefan Beller <stefanbeller@googlemail.com>,
Philip Oakley <philipoakley@iee.org>,
Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Marc Branchaud <marcnarc@xiplink.com>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCHv3] git-tag man: when to use lightweight or annotated tags
Date: Mon, 29 Jul 2013 20:16:03 +0200 [thread overview]
Message-ID: <51F6B163.8000605@gmail.com> (raw)
In-Reply-To: <51F3B2D1.2040402@googlemail.com>
On 07/27/2013 01:45 PM, Stefan Beller wrote:
> On 07/27/2013 01:26 PM, Philip Oakley wrote:
>
>> Try 'git format-patch' and 'git send-email'. The format-patch man page
>> even has a note about Thunderbird corruptions.
>>
>> Philip
>>
>
> Well I use Thunderbird as well for regular communication except for
> sending patches.
> The kernel documentation has also some words about Thunderbird
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/email-clients.txt
>
> Given so many steps, I also configured git send-email, which makes
> sure that patches are uncorrupted.
> For gmail add these lines to your ~/.gitconfig
>
> [sendemail]
[snip]
>
> Then you'd need to have msmtp installed and have the following
> in the file ~/.msmtprc
[snip]
>
> I think it would also work without having git relying on msmtp by now,
> but I'd be too lazy to change my existing working setup.
>
Hi Paolo, Philip, Stefan,
thank you, you've been very kind.
I think I've set it up, I'll try with the next patch, if any!
Regards,
Daniele Segato
next prev parent reply other threads:[~2013-07-29 18:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 10:17 git tag usability issue: Lightweight vs Annotated confusion for the end user (ex. git describe default) Daniele Segato
2013-07-24 20:34 ` Junio C Hamano
2013-07-25 13:45 ` [PATCH] git-tag man: when to use lightweight or annotated tags Daniele Segato
2013-07-25 14:47 ` Marc Branchaud
2013-07-26 8:44 ` Daniele Segato
2013-07-26 8:46 ` Daniele Segato
2013-07-26 14:51 ` Marc Branchaud
2013-07-26 17:19 ` Daniele Segato
2013-07-26 17:33 ` [PATCHv3] " Daniele Segato
2013-07-26 19:06 ` Jeff King
2013-07-26 19:36 ` Jonathan Nieder
2013-07-29 18:02 ` Daniele Segato
2013-08-07 12:32 ` Daniele Segato
2013-07-26 21:13 ` Marc Branchaud
2013-07-29 15:04 ` Junio C Hamano
2013-07-29 18:20 ` Daniele Segato
2013-07-27 10:39 ` Daniele Segato
2013-07-27 11:26 ` Philip Oakley
2013-07-27 11:45 ` Stefan Beller
2013-07-29 18:16 ` Daniele Segato [this message]
2013-07-26 21:13 ` [PATCH] " Marc Branchaud
2013-07-29 18:21 ` Daniele Segato
2013-07-25 13:48 ` git tag usability issue: Lightweight vs Annotated confusion for the end user (ex. git describe default) Daniele Segato
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51F6B163.8000605@gmail.com \
--to=daniele.segato@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=marcnarc@xiplink.com \
--cc=paolo.ciarrocchi@gmail.com \
--cc=philipoakley@iee.org \
--cc=stefanbeller@googlemail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).