Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Thomas Osterried <thomas@osterried.de>
To: "Steven R. Loomis" <srl295@gmail.com>
Cc: "Mike McCarthy, W1NR" <lists@w1nr.net>, linux-hams@vger.kernel.org
Subject: Re: Replacement for linux-ax25.org git?
Date: Tue, 8 Nov 2022 19:10:06 +0100	[thread overview]
Message-ID: <Y2qbfrHkKAf44cdK@x-berg.in-berlin.de> (raw)
In-Reply-To: <29F7FF8E-64E6-4927-9DE6-23E98C763832@gmail.com>

Hello Steven,

On Tue, Nov 08, 2022 at 11:50:42AM -0600, Steven R. Loomis wrote:
> Thanks for bringing this back.
> 
> “Latest Versions” on the main page right hand sidebar <http://linux-ax25.in-berlin.de/wiki/Main_Page> still link to the linux-ax25.org <http://linux-ax25.org/> URL and are thus broken.

Thank you.

It's recommended to use the git head anyway.


I'll fix the links in the wiki.
But personaly, I really dislike the "releases"-idea in the days of git.
It's much easier to initiate "git pull" to update a previously checked-out
version.
Furthermore, if we really like to to have something like "release", we need a
mechanism that (semi-)automatically makes a new release some time after
a commit (that has been proven bug-free).
Else there's no benefit of using such a "release" in production, because it
remained old and buggy.

vy 73,
	- Thomas  dl9sau


  parent reply	other threads:[~2022-11-08 18:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08 12:41 Replacement for linux-ax25.org git? Dave Hibberd
2022-11-08 13:41 ` Mike McCarthy, W1NR
2022-11-08 15:14   ` Thomas Osterried
2022-11-08 17:52     ` Steven R. Loomis
     [not found]     ` <29F7FF8E-64E6-4927-9DE6-23E98C763832@gmail.com>
2022-11-08 18:10       ` Thomas Osterried [this message]
2022-11-08 23:28         ` Dave Hibberd
2022-11-10  2:03 ` John Weaver

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=Y2qbfrHkKAf44cdK@x-berg.in-berlin.de \
    --to=thomas@osterried.de \
    --cc=linux-hams@vger.kernel.org \
    --cc=lists@w1nr.net \
    --cc=srl295@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