From: Oliver Hartkopp <socketcan@hartkopp.net>
To: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: MOVED TO GITHUB: Linux-CAN user space source repositories
Date: Thu, 05 Mar 2015 20:06:27 +0100 [thread overview]
Message-ID: <54F8A933.1040309@hartkopp.net> (raw)
In-Reply-To: <CAGm1_ksdokuRQ8kAfX+EsjYAzZj3UXn5XH2duS2TMX_NjaYnUg@mail.gmail.com>
As Gitorious is to be acquired by GitLab and gitorious.org will shut down at
end of May the Linux-CAN / SocketCAN git repositories have to be moved away
from https://gitorious.org/linux-can/
As many of you already have a GitHub account Marc and I agreed on following
Yegors suggestion to move the Linux-CAN / SocketCAN repos to GitHub.
You can now find the Linux-CAN repositories at:
https://github.com/linux-can/
The repositories are moved & rearranged from gitorious.org as shown below:
Linux-CAN / SocketCAN user space applications
https://github.com/linux-can/can-utils/
Linux-CAN / SocketCAN testing applications
https://github.com/linux-can/can-tests/
Firmware for supported CAN adapters
https://github.com/linux-can/can-firmware/
Linux-CAN / SocketCAN logos
https://github.com/linux-can/can-logos/
Linux-CAN / SocketCAN miscellaneous stuff
https://github.com/linux-can/can-misc/
The can-modules repository was not moved as this network layer stuff mostly
puzzled people who built the sources without success on recent systems. As
most of the network layer CAN protocols are already in Linux mainline, I moved
can-modules to a 'private' repository to continue my ISO 15765-2:2015 protocol
development:
Obsolete CAN network layer modules *ONLY* used for ISO 15765-2 development now
https://github.com/hartkopp/can-isotp-modules/
This repo will stay there but it is now separated from user space resources.
If you have forked repos or other code on gitorious which relies on the former
repository setup make sure not to lose your work when gitorious shuts down in
May. From now on the development will only continue on GitHub.
Have fun!
Oliver
On 03.03.2015 22:35, Yegor Yefremov wrote:
> Does it effect us? Should can-utils move to github?
>
> http://lwn.net/Articles/635358/rss
>
> Yegor
next prev parent reply other threads:[~2015-03-05 19:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 21:35 GitLab and Gitorious Yegor Yefremov
2015-03-03 22:04 ` Marc Kleine-Budde
2015-03-05 19:06 ` Oliver Hartkopp [this message]
2015-03-06 7:41 ` MOVED TO GITHUB: Linux-CAN user space source repositories Robert Schwebel
2015-03-06 7:56 ` Marc Kleine-Budde
2015-03-06 8:03 ` Marc Kleine-Budde
2015-03-06 11:33 ` Oliver Hartkopp
2015-03-06 13:48 ` Marc Kleine-Budde
2015-03-06 15:04 ` Oliver Hartkopp
2015-03-20 10:03 ` Laurent Vaudoit
2015-03-20 17:56 ` Oliver Hartkopp
2015-03-24 20:29 ` Kurt Van Dijck
2015-04-21 10:20 ` moved to github: linux can-j1939 sources 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=54F8A933.1040309@hartkopp.net \
--to=socketcan@hartkopp.net \
--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.