Linux CAN drivers development
 help / color / mirror / Atom feed
From: Alexander Gerasiov <gq@cs.msu.su>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: 890090@bugs.debian.org,
	Fabian Inostroza <soulsonceonfire@gmail.com>,
	linux-can <linux-can@vger.kernel.org>
Subject: Re: Bug#890090: can-utils: Please update, new features and tools in upstream
Date: Sun, 11 Feb 2018 22:56:30 +0300	[thread overview]
Message-ID: <20180211225630.7788bb18@brick.gerasiov.net> (raw)
In-Reply-To: <1928b968-0bc9-beaf-abd9-7158ab6b4f4b@pengutronix.de>

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

Hello Marc,

On Sun, 11 Feb 2018 14:45:34 +0100
Marc Kleine-Budde <mkl@pengutronix.de> wrote:

> On 02/11/2018 10:53 AM, Alexander Gerasiov wrote:
> > Once again I recommend you to tag releases in git. This
> > automatically pings package maintainers in various Linux
> > distributions to update their packages. =)  
> 
> Done, I've created a tag and pushed it to github.

Great job, thanks. I've just updated Debian package and added watch file
to follow releases.

I have also added autogenerated manpages in this release, will make
pull request on github a little bit later.

-- 
Best regards,
 Alexander Gerasiov

 Contacts:
 e-mail: gq@cs.msu.su  WWW: http://gerasiov.net  Telegram/Skype:
 gerasiov PGP fingerprint: 04B5 9D90 DF7C C2AB CD49  BAEA CA87 E9E8
 2AAC 33F1

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

      reply	other threads:[~2018-02-11 19:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <151831023087.7397.10489186056134209003.reportbug@debian>
2018-02-11  9:53 ` Bug#890090: can-utils: Please update, new features and tools in upstream Alexander Gerasiov
2018-02-11 13:45   ` Marc Kleine-Budde
2018-02-11 19:56     ` Alexander Gerasiov [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=20180211225630.7788bb18@brick.gerasiov.net \
    --to=gq@cs.msu.su \
    --cc=890090@bugs.debian.org \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=soulsonceonfire@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