On 2008-06-26 12:27:39 +0200, Flavio Poletti wrote:
> When I was happy with the modifications, I used git-format-patch to
> produce the message and the patch to send. I then saw that the
> format is a little different with respect to what diff -u produces;
> in particular, I noticed that there was an added line between the
> "diff --git..." line and the one stating the "origin" file:
>
> diff --git a/glib/gstrfuncs.c b/glib/gstrfuncs.c
> *** this one *** index 61d11ed..7786f10 100644
> --- a/glib/gstrfuncs.c
> +++ b/glib/gstrfuncs.c
patch ignores any junk it doesn't understand, including this line.
> Moreover, each chunk's header contained added stuff, like the
> "g_ascii_strtoll..." stuff in the following example line:
>
> @@ -813,6 +813,8 @@ g_ascii_strtoll (const gchar *nptr,
You get this by giving the -p flag to GNU diff; git diff just does it
by default, is all.
> 4. some hints to use git for working on projects that do not use any
> other VCS, or for which one only wants to produce and send a quick
> patch starting from a tarball.
You can use git/contrib/fast-import/import-tars.perl to import the
last few releases into git (possibly just the last release, if you
don't need the history) and then just build on that, and send patches
back to the project when you're done.
When the project makes another release, use import-tars to import the
new tarball, and then rebase if you have any patches they haven't
accepted yet.
--
Karl Hasselström, kha@xxxxxxxxxxx
www.treskal.com/kalle
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
