On 05/08/2014 01:44 AM, Dan Carpenter wrote:
> These days most people use git to send patches so I have added a section
> about that.
>
> Signed-off-by: Dan Carpenter
> ---
> v2: Fixed changelog
>
> diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
> index 4e30eba..9
On Thu, May 08, 2014 at 05:28:46PM +0800, Hillf Danton wrote:
> And a howto to tame gmail is doule apprecaited.
There is actually a gmail section in the man page. `man git send-email`
It's a the bottom.
EXAMPLE
Use gmail as the smtp server
To use git send-email to send your patches th
On Fri, May 09, 2014 at 09:24:56AM +0900, Namhyung Kim wrote:
> > +Git
> > +--
> > +These days most developers use `git send-email` instead of regular
> > +email clients. On the receiving end, maintainers use `git am` to
> > +appl
Hi Dan,
On Thu, 8 May 2014 11:44:12 +0300, Dan Carpenter wrote:
> These days most people use git to send patches so I have added a section
> about that.
>
> Signed-off-by: Dan Carpenter
> ---
> v2: Fixed changelog
>
> diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
On Thu, May 8, 2014 at 5:05 PM, Julian Andres Klode wrote:
> On Thu, May 08, 2014 at 11:44:12AM +0300, Dan Carpenter wrote:
>> +as raw text including all the headers. Run `cat raw_email.txt | git am`
>
> `cat raw_email.txt | git am` seems a bit pointless. Why not simply
> `git am raw_email.txt`?
On Thu, May 08, 2014 at 11:44:12AM +0300, Dan Carpenter wrote:
> +as raw text including all the headers. Run `cat raw_email.txt | git am`
`cat raw_email.txt | git am` seems a bit pointless. Why not simply
`git am raw_email.txt`? `git am < raw_email.txt` does the same too
and avoids the useless ca
These days most people use git to send patches so I have added a section
about that.
Signed-off-by: Dan Carpenter
---
v2: Fixed changelog
diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt
index 4e30eba..9004a5fd 100644
--- a/Documentation/email-clients.txt
+++ b/Docu
7 matches
Mail list logo
