From: 'Sascha Hauer' <s.hauer@pengutronix.de>
To: Kevin Du Huanpeng <u74147@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: v2013.12.0
Date: Fri, 6 Dec 2013 10:28:10 +0100 [thread overview]
Message-ID: <20131206092810.GA24559@pengutronix.de> (raw)
In-Reply-To: <000001cef261$1f716e00$5e544a00$@gmail.com>
Hi Kevin,
On Fri, Dec 06, 2013 at 04:56:54PM +0800, Kevin Du Huanpeng wrote:
> arch/x86/lib/barebox.lds
> add this file to .gitignore....
> - - -
> dev@bogon:~/barebox$ git status
> # On branch master
> # Untracked files:
> # (use "git add <file>..." to include in what will be committed)
> #
> # arch/x86/lib/barebox.lds
> nothing added to commit but untracked files present (use "git add" to track)
We normally communicate changes to barebox with patches. So if you want
to have something changed in barebox you should send patches. For doing
so you should read Documentation/SubmittingPatches in the Linux Kernel
(Some of this may be outdated, but most of it is true and applies to
barebox aswell)
As a git user the techincal stuff probably goes down to:
git checkout origin/master -b myworkbranch
<commit changes>
git send-email --to "barebox@lists.infradead.org" origin/master
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2013-12-06 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 8:05 v2013.12.0 Sascha Hauer
2013-12-06 8:56 ` v2013.12.0 Kevin Du Huanpeng
2013-12-06 9:28 ` 'Sascha Hauer' [this message]
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=20131206092810.GA24559@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=u74147@gmail.com \
/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