From: "Junio C Hamano"
"Philip Oakley" writes:
It still means that my patch is incomplete in its aim to bring out
these possible broader usages.
I haven't yet looked at the mail archives to see if there is more
around the time of those introductions.
From: "Junio C Hamano"
"Philip Oakley" writes:
It still means that my patch is incomplete in its aim to bring out
these possible broader usages.
I haven't yet looked at the mail archives to see if there is more
around the time of those introductions.
From: "Jacob Keller"
Hi,
On Sat, Sep 12, 2015 at 3:51 PM, Philip Oakley
wrote:
The branch description will be included in 'git format-patch
--cover-letter' and in 'git pull-request' emails. Tell the reader.
While here, clarify that the
From: "Philip Oakley"
From: "Jacob Keller"
Hi,
On Sat, Sep 12, 2015 at 3:51 PM, Philip Oakley
wrote:
The branch description will be included in 'git format-patch
--cover-letter' and in 'git pull-request' emails. Tell the
"Philip Oakley" writes:
> It still means that my patch is incomplete in its aim to bring out
> these possible broader usages.
>
> I haven't yet looked at the mail archives to see if there is more
> around the time of those introductions.
I guess this is largely my fault,
Hi,
On Sat, Sep 12, 2015 at 3:51 PM, Philip Oakley wrote:
> The branch description will be included in 'git format-patch
> --cover-letter' and in 'git pull-request' emails. Tell the reader.
>
> While here, clarify that the description may be a multi-line
> explanation of
6 matches
Mail list logo