public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Anton Mikanovich <amikan@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: isar git repository - hash changed
Date: Fri, 25 Nov 2022 09:41:59 +0100	[thread overview]
Message-ID: <CAJGKYO4OnbtGW6X0HY2LmiQLpk4cdHavG+i_mnj53xRJK6260Q@mail.gmail.com> (raw)
In-Reply-To: <2eb581dd-a431-c004-d161-3e0ed639462c@ilbers.de>

On Fri, 25 Nov 2022 at 09:30, Anton Mikanovich <amikan@ilbers.de> wrote:
>
> 25.11.2022 11:05, Roberto A. Foglietta wrote:
> > Hello Anton,
> >
> >   I cannot find that commit anymore
> >
> >   git log --all | grep f61db1b
> >
> >   Probably it was my mistake to set my project on a develop branch.
> >
> >   Thanks for having specified that also the branch "next" is a stable
> > one and not a developing one.
> >
> >   Best regards, R-
>
> Please take a look at CONTRIBUTING.md documentation.
> It wasn't updated for a long time but still can help both users and
> contributors to understand how Isar being updated.
>

I saw the document, the following and there is a typo about Continuous:

next is a branch for CI (Continous Integration), testing and early feedback.

means that - if a commit does not pass the CI, testing or users review
(feedback), it could be removed?

So, the "next" is not a stable branch in the sense that every hash in
it will remain forever. Isn't that right?

While in the master branch every commit (hash) remains forever. Is that right?

Best regards, R-

  reply	other threads:[~2022-11-25  8:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 23:54 Roberto A. Foglietta
2022-11-25  6:50 ` Anton Mikanovich
2022-11-25  8:05   ` Roberto A. Foglietta
2022-11-25  8:30     ` Anton Mikanovich
2022-11-25  8:41       ` Roberto A. Foglietta [this message]
2022-11-25  8:50         ` Baurzhan Ismagulov
2022-11-25  9:04           ` Roberto A. Foglietta
2022-11-25  8:58         ` Anton Mikanovich

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=CAJGKYO4OnbtGW6X0HY2LmiQLpk4cdHavG+i_mnj53xRJK6260Q@mail.gmail.com \
    --to=roberto.foglietta@gmail.com \
    --cc=amikan@ilbers.de \
    --cc=isar-users@googlegroups.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