Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Minicom git Repo and new version
Date: Tue, 31 Jul 2018 23:17:25 +0200	[thread overview]
Message-ID: <20180731231725.638cbe53@windsurf> (raw)
In-Reply-To: <46fe66d9-b985-c338-2b84-376646793542@micronovasrl.com>

Hello,

On Tue, 31 Jul 2018 22:59:02 +0200, Giulio Benetti wrote:

> Adam(Minicom Maintainer) in Cc set up a repository for Minicom here:
> https://salsa.debian.org/minicom-team/minicom
> 
> Some fix and support s485 has been added since last package version.
> Most of all, now it's under git,
> so I wanted to ask if it would help if I create a patch managing Minicom 
> package as a git(possibly using github helper) and bumping version to 
> the last git commit.
> Or create new package based on git using same version as now.
> Or wait for Adam to tag a real version to do everything once.

Yes, you can send an update to use this new Git repository. It will of
course be even better when Adam does a tagged release, but in the mean
time, we can use a random Git commit especially if there's a good
justification behind it (RS485 support for example).

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-07-31 21:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-31 20:59 [Buildroot] Minicom git Repo and new version Giulio Benetti
2018-07-31 21:17 ` Thomas Petazzoni [this message]
2018-07-31 22:18   ` Giulio Benetti

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=20180731231725.638cbe53@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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