public inbox for lm-sensors@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean-Marc Pigeon <jmp@safe.ca>
To: lm-sensors@vger.kernel.org
Subject: Re: github , lm-sensors tag release
Date: Fri, 23 Nov 2018 15:32:08 +0000	[thread overview]
Message-ID: <5BF81D78.7030809@safe.ca> (raw)
In-Reply-To: <5BF81448.2060108@safe.ca>

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

Hello,
Thanks for this quick reply.
On 11/23/2018 10:20 AM, Ondřej Lysoněk wrote:
> Hi,
>
> On 23. 11. 18 15:52, Jean-Marc Pigeon wrote:
>> Hello,
>>
>> Working to use the last lm-sensors stable version
>> from github, to be use within LFS (Linux from scratch
>> project).
>>
>> Seen the last tag is v3-4-0, 3 year old.
>>
>> Is there another way to git-archive the last stable
>> version?
>
> Well, you can use e.g. the following to archive the master branch. The
> master branch should be fine to use. Is that what you're asking?
> git archive --prefix lm-sensors-3.4.1/ -o lm-sensors-3.4.1.tar.gz master
>

Sure I can do that, but then it is "mine" 3.4.1 version, better
then to use the day (ie, 3.4.20181123)
>>
>> How do you tag version, such everybody is on the
>> same page when speaking about lm-sensors release?
>>
>
> The next release, 3.5.0, is coming soon and it will be tagged as V3-5-0
> in git.
Good..
IMHO,  project should have more often tagging, 3 year is
too long.
- Tide schedule tagging, mean the project is well and alive
- This will mark stable version, as deemed by project manager.
My 2 cents.

>
> Best regards
> Ondřej Lysoněk
>


-- 

A bientôt
===========================================================
Jean-Marc Pigeon                        E-Mail: jmp@safe.ca
SAFE Inc.                             Phone: (514) 493-4280
   Clement, 'a kiss solution' to get rid of SPAM (at last)
      Clement' Home base <"http://www.clement.safe.ca">
===========================================================


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5160 bytes --]

      parent reply	other threads:[~2018-11-23 15:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23 14:52 github , lm-sensors tag release Jean-Marc Pigeon
2018-11-23 15:20 ` Ondřej Lysoněk
2018-11-23 15:32 ` Jean-Marc Pigeon [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=5BF81D78.7030809@safe.ca \
    --to=jmp@safe.ca \
    --cc=lm-sensors@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