linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Cc: dschanoeh@googlemail.com
Subject: Re: [Gitorious] Activity: dschanoeh updated merge request for...
Date: Tue, 29 Nov 2011 15:08:13 +0100	[thread overview]
Message-ID: <4ED4E74D.3090608@pengutronix.de> (raw)
In-Reply-To: <20111129121452.B4F9F7590F@steelheart.shortcut.kunder.linpro.no>

[-- Attachment #1: Type: text/plain, Size: 1559 bytes --]

Hello * and dschanoeh,

On 11/29/2011 01:14 PM, Gitorious wrote:
> ------------------------------------------------------------------------
> dschanoeh updated merge request for dschanoehs-can-utils with can-utils.
> The merge request is at http://gitorious.org/linux-can/can-utils/merge_requests/1
> ------------------------------------------------------------------------

I just received this pull request from you. It basically consists of
* removing plain old Makefile
* fixes for the old include directory

Regarding removing Makefile, fine with me, Oliver what do you think?

I've started some time ago to import the includes from the svn into the
git, but kernel only includes were still left. Now I just updated my git
repo which merges the includes and adopts both Makefile and autotools.

There is a squashed version, which imports the includes without their
history. This branch is called master-squashed.

Please checkout the master branch (or master-squashed) of my repo and test:
https://gitorious.org/~bet-frogger/linux-can/mkl-can-utils

There is a j1939 branch, too.

Please test and comment, if everything works I want to commit either my
master branch or master-squashed to the official repo, which branch is
better?

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   |


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

       reply	other threads:[~2011-11-29 14:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111129121452.B4F9F7590F@steelheart.shortcut.kunder.linpro.no>
2011-11-29 14:08 ` Marc Kleine-Budde [this message]
     [not found]   ` <CAEuXk91Bh+Z0yTqQebmW-EmrU59c-dFz_zKj8ky0ssgFBy23bQ@mail.gmail.com>
2011-12-03 18:54     ` [Gitorious] Activity: dschanoeh updated merge request for Marc Kleine-Budde
2011-12-04  9:57       ` Jan-Niklas Meier
2011-12-05 10:28         ` Marc Kleine-Budde
2011-12-05 10:30         ` Marc Kleine-Budde
2011-12-05 17:59           ` Jan-Niklas Meier

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=4ED4E74D.3090608@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=dschanoeh@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).