threads / discuss / 3853

how to make a git-format patch

Subject: how to make a git-format patch

## tl;dr

5 messages between Apr 12, 2006 and Apr 13, 2006.

replies: 4people: 4as markdown or json

Aubrey· Apr 12, 2006, 10:28 UTC · lore

Hi list,

When I use GIT to generate a patch, I can use git-diff, if one file changed, I can get the following patch: =================================

diff --git a/net/packet/Kconfig b/net/packet/Kconfig
index 34ff93f..959c272 100644
--- a/net/packet/Kconfig
+++ b/net/packet/Kconfig
@@ -17,7 +17,7 @@ config PACKET

 config PACKET_MMAP
        bool "Packet socket: mmapped IO"
-       depends on PACKET
+       depends on PACKET && MMU
        help
          If you say Y here, the Packet protocol driver will use an IO
          mechanism that results in faster communication.
=================================
But I saw most of the git-format patches have a header in the front of
the patch file, like:
=================================
 * Added xxxxxx support

Signed-off-by: xxxxxxxx <xxxxxxx@email.com>
---

 net/packet/Kconfig |   11 ++++++++++-
 1 files changed, 10 insertions(+), 1 deletions(-)

diff --git a/net/packet/Kconfig b/net/packet/Kconfig
index 34ff93f..959c272 100644
--- a/net/packet/Kconfig
+++ b/net/packet/Kconfig

----snip----
=================================

Just want to know how this kind of patch format generated.
Thanks for any hints.

Regards,
-Aubrey

Jakub Narebski· Apr 12, 2006, 11:12 UTC · re: Aubrey · lore

Re: how to make a git-format patch

Aubrey wrote:

Show 21 quoted lines

> But I saw most of the git-format patches have a header in the front of
> the patch file, like:
> =================================
>  * Added xxxxxx support
> 
> Signed-off-by: xxxxxxxx <xxxxxxx@email.com>
> ---
> 
>  net/packet/Kconfig |   11 ++++++++++-
>  1 files changed, 10 insertions(+), 1 deletions(-)
> 
> diff --git a/net/packet/Kconfig b/net/packet/Kconfig
> index 34ff93f..959c272 100644
> --- a/net/packet/Kconfig
> +++ b/net/packet/Kconfig
> 
> ----snip----
> =================================
> 
> Just want to know how this kind of patch format generated.
> Thanks for any hints.

Perhaps git-format-patch(1) is what you want?

-- 
Jakub Narebski
Warsaw, Poland

Mathieu Chouquet-Stringer· Apr 12, 2006, 14:04 UTC · re: Aubrey · lore

Re: how to make a git-format patch

aubreylee@gmail.com (Aubrey) writes:

> But I saw most of the git-format patches have a header in the front of
> the patch file, like:

I believe you're talking about 'git whatchanged -p' which not only displays the diffs but also the commit comments.

-- 
Mathieu Chouquet-Stringer

Aubrey· Apr 13, 2006, 05:36 UTC · re: Mathieu Chouquet-Stringer · lore

Re: how to make a git-format patch

On 12 Apr 2006 16:04:16 +0200, Mathieu Chouquet-Stringer <ml2news@free.fr> wrote:

> I believe you're talking about 'git whatchanged -p' which not only displays
> the diffs but also the commit comments.

git whatchanged -p didn't include the signoff and howmany lines changed which git-format-patch seems not include commit comments.

Is there one command to merge the two kind of message?

Thanks, -Aubrey

Junio C Hamano· Apr 13, 2006, 05:53 UTC · re: Aubrey · lore

Re: how to make a git-format patch

Aubrey <aubreylee@gmail.com> writes:

> git whatchanged -p didn't include the signoff and howmany lines
> changed which git-format-patch seems not include commit comments.
>
> Is there one command to merge the two kind of message?

I think you already guessed it, judging from the Subject: line, but the command is called "git-format-patch", and was around for a long time.