On Tuesday 13 October 2009, Øyvind Harboe wrote:
> On Tue, Oct 13, 2009 at 8:57 PM, David Brownell <[email protected]> wrote:
> > On Tuesday 13 October 2009, Øyvind Harboe wrote:
> >> > If so, a diff follows. I've never submitted a diff before, so I'm not
> >> > sure
> >> > if I did it the right way around.
> >
> > "git diff > my.patch"
> > .... then edit it to provide a good description, and remove cruft
>
> These patches are not as nice since I can't "git am" them?
Save the email from which you received such a patch. Given that the
description is good (and it's fair to edit them when they need fixes,
like shortening lines, fixing grammar, removing cruft) ... it's the
canonical input for git-am!
... stuff
From: Colin <[email protected]>
...
Subject: one-line patch summary
...
<longer patch description>
---
metadata ... diffstat output, comments not-for-the-repository, etc
<git diff output>
Broadly, there are two classes of patch submitter. Most folk are
closer to Colin's situation: not heavy patch submitters, maybe not
even primarily a developer. At the other extreme are folk who put
out lots of patches and need tools to manage them all ... tools like
quilt, git, stkgit, and so on.
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
