From: Kurt Van Dijck <kurt.van.dijck-/BeEPy95v10@public.gmane.org>
To: Marc Kleine-Budde <mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
Cc: socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
Oliver Hartkopp
<socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>,
Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>,
linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: git repos @ gitorious.org
Date: Mon, 7 Nov 2011 09:07:25 +0100 [thread overview]
Message-ID: <20111107080712.GA279@e-circ.dyndns.org> (raw)
In-Reply-To: <4EB69430.7070801-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
On Sun, Nov 06, 2011 at 03:05:36PM +0100, Marc Kleine-Budde wrote:
> On 11/04/2011 05:16 PM, Kurt Van Dijck wrote:
> > On Thu, Nov 03, 2011 at 02:08:41PM +0100, Kurt Van Dijck wrote:
> >> On Wed, Nov 02, 2011 at 11:16:18PM +0100, Marc Kleine-Budde wrote:
> >>> On 11/02/2011 09:12 PM, Oliver Hartkopp wrote:
> >>>>
> >>>> https://gitorious.org/~<kurts_account>/linux-can/can-modules-j1939
> >>>> https://gitorious.org/~<kurts_account>/linux-can/can-utils-j1939
> >
> > Since the can-j1939-modules require one to use a modified iproute2,
> > I wanted to create an iproute-j1939 within linux-can, but I see no way
> > to accomplish this.
> >
> > Any opinions on how to proceed?
>
> Google for the iproute2 git upstream, clone it, modify it. Create a
> iproute2 git repo on gitorious, push your changes there.
I see not how to create on Gitorious a linux-can/iproute2-can-j1939
or similar. It looks to me as if I need to create a project first.
>
> The git workflow is basically the same as you did to copy the j1939
> can-utils to your repo.
>
> Finally send a pull request to the iprout2 upstream.
>
> cheers, 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 |
>
next prev parent reply other threads:[~2011-11-07 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EB1A448.6000703@hartkopp.net>
[not found] ` <4EB1C132.2070103@pengutronix.de>
[not found] ` <20111103130841.GG317@e-circ.dyndns.org>
[not found] ` <20111103130841.GG317-MxZ6Iy/zr/UdbCeoMzGj59i2O/JbrIOy@public.gmane.org>
2011-11-04 16:16 ` git repos @ gitorious.org Kurt Van Dijck
[not found] ` <20111104161655.GC18026-MxZ6Iy/zr/UdbCeoMzGj59i2O/JbrIOy@public.gmane.org>
2011-11-06 14:05 ` Marc Kleine-Budde
[not found] ` <4EB69430.7070801-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-11-07 8:07 ` Kurt Van Dijck [this message]
[not found] ` <20111107080712.GA279-MxZ6Iy/zr/UdbCeoMzGj59i2O/JbrIOy@public.gmane.org>
2011-11-07 8:10 ` Marc Kleine-Budde
[not found] ` <4EB79288.5010409-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-11-07 8:32 ` Kurt Van Dijck
2011-11-07 8:54 ` Marc Kleine-Budde
2011-11-07 9:00 ` Marc Kleine-Budde
2011-11-07 10:31 ` Kurt Van Dijck
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=20111107080712.GA279@e-circ.dyndns.org \
--to=kurt.van.dijck-/beepy95v10@public.gmane.org \
--cc=linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mkl-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
--cc=socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=socketcan-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org \
--cc=wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.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