From: Kristoffer Ericson <kristoffer.ericson@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] SH/Dreamcast - improve detection of attached
Date: Thu, 14 Feb 2008 09:34:20 +0000 [thread overview]
Message-ID: <20080214103420.73ec6c89.Kristoffer.ericson@gmail.com> (raw)
In-Reply-To: <1202689502.6237.23.camel@localhost.localdomain>
On Tue, 12 Feb 2008 10:23:40 -0500
Mike Frysinger <vapier@gentoo.org> wrote:
> is there a reason you guys dont use git to submit your patches ? it does take
> time to learn if you arent familiar, but the time spent more than pays off in
> the long wrong ... it takes care of all these fun bits for you. a shortened
> list for arbitrary developers:
I use git daily to maintain the jlime kernel source repository, don't use it to create patches though.
> 1. < make changes to git repo >
> 2. git add < files you want to commit >
> 3. git commit -s
> - first line is the subject (so you have to follow convention yourself)
> - one blank line
> - paragraph for body of changelog
> so the example commit log would be (just the stuff between the dashes):
> ----------------------------
> SH/Maple/Dreamcast: improve detection of attached peripherals
>
> Blah blah blah this is the long subject explaining why this is wanted.
>
> Signed-off-line: automatically-added-by-the-s-flag
> ----------------------------
> 4. git-format-patch HEAD^
This assumes that your patch is the only diff against current HEAD right? I have loads of changes, so need
to pick out the certain commit. I usually do "git diff origin > mypatch.patch" The format patch adds other stuff?
> 5. git-send-email --to linux-sh@vger.kernel.org <list of patches produced>
That I should use more often.
> 6. git reset --hard HEAD^
>
> i'm lazy and dont create branches for the small one-off changes. so you guys
> doing more work would probably want to create a branch before doing the work.
> in that case, just replace "HEAD^" with like "master" to generate patches of
> all the commits made to your branch.
> -mike
>
My repositories are based on linus tree, but I should create a branch towards linux-sh (got seperate tree for that).
Big thanks for tips, I guess its worth learning all aspects of git.
next prev parent reply other threads:[~2008-02-14 9:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 0:25 [PATCH] SH/Dreamcast - improve detection of attached peripherals Adrian McMenamin
2008-02-12 8:24 ` Paul Mundt
2008-02-12 9:36 ` [PATCH] SH/Dreamcast - improve detection of attached Kristoffer Ericson
2008-02-12 9:48 ` [PATCH] SH/Dreamcast - improve detection of attached peripherals Paul Mundt
2008-02-12 15:23 ` Mike Frysinger
2008-02-13 13:24 ` [PATCH] SH/Dreamcast - improve detection of attached Adrian McMenamin
2008-02-13 13:30 ` Adrian McMenamin
2008-02-14 9:34 ` Kristoffer Ericson [this message]
2008-02-14 10:14 ` [PATCH] SH/Dreamcast - improve detection of attached peripherals Paul Mundt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080214103420.73ec6c89.Kristoffer.ericson@gmail.com \
--to=kristoffer.ericson@gmail.com \
--cc=linux-sh@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox