From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Giox79 <giovanniparodi79@gmail.com>, linux-can@vger.kernel.org
Subject: Re: CAN j1939 library doubts
Date: Fri, 15 Mar 2013 11:33:45 +0100 [thread overview]
Message-ID: <5142F909.5070007@pengutronix.de> (raw)
In-Reply-To: <20130314210751.GC1387@vandijck-laurijssen.be>
[-- Attachment #1: Type: text/plain, Size: 1697 bytes --]
On 03/14/2013 10:07 PM, Kurt Van Dijck wrote:
> On Thu, Mar 14, 2013 at 04:20:08PM +0000, Giox79 wrote:
>> Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:
>>
>> In order to integrate your libs to my kernel, I was supposing to make a diff
>> between source file, looking mainly at can and iproute2, merge the diffs and
>> build the whole system.
>> Do you think this is the right approach?
> no. I (just) prepared the repositories to allow easy merges.
>
> follow these steps (@Marc, can you just verify the 'git' calls):
:) Looks good.
> git clone your kernel, or get a stable one
> $ git clone http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> ... this takes time
> $ cd linux-stable
> $ git tag
> choose a version, like v3.3, or v3.8, ...
> $ git checkout <chosen-version>
> $ git checkout -b <new-branch-name>
> This last command creates a new branch, so you can play freely.
> Now choose your branch on http://gitorious.org/~kurt-vd/linux-can/linux-can-j1939
> , like j1939-v3.3
> $ git pull git://gitorious.org/~kurt-vd/linux-can/linux-can-j1939.git <gitorious-branch-name>
I would add Kurt's tree as a remote, instead of pull do:
git remote add -f kurt git://gitorious.org/~kurt-vd/linux-can/linux-can-j1939.git
git merge kurt/<gitorious-branch-name>
If you already have a git tree, you can start with the "git remote add".
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-03-15 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 21:52 CAN j1939 library doubts Giox79
2013-03-13 8:29 ` Jean-Claude Monnin
2013-03-13 8:42 ` Kurt Van Dijck
2013-03-14 11:17 ` Giox79
2013-03-14 12:20 ` Kurt Van Dijck
2013-03-14 16:20 ` Giox79
2013-03-14 21:07 ` Kurt Van Dijck
2013-03-15 10:27 ` Giox79
2013-03-15 10:33 ` Marc Kleine-Budde [this message]
2013-03-16 9:35 ` Giox79
2013-03-14 11:17 ` Giox79
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=5142F909.5070007@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=giovanniparodi79@gmail.com \
--cc=linux-can@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.