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:05:09 +0100	[thread overview]
Message-ID: <CAJGKYO6_BZJMVcivK_wJdFqmmDH_=gku4NGk8Hw8uyrGSB5M6A@mail.gmail.com> (raw)
In-Reply-To: <cd9c0073-a0d6-8d39-59f0-08c4f488c167@ilbers.de>

On Fri, 25 Nov 2022 at 07:50, Anton Mikanovich <amikan@ilbers.de> wrote:
>
> 25.11.2022 02:54, Roberto A. Foglietta wrote:
> > Hi all,
> >
> > this hash has been changed and it did not exist anymore in the repository
> >
> > -    refspec: f61db1b298e2c26fef61fa8efae55e5393b5f185
> > +    refspec: 3849087ea7c6424b9c688518005c16ef83365528
> >
> > Did it a rebase?
> >
> > Best regards, R-
> >
> Hello Roberto,
>
> This commit (f61db1b CI: expect a message about filesystem resize vom
> expand script)
> has never been included into 'master' or 'next' branches. Moreover the
> patchset
> will not been merged to 'next' in the current state, because it didn't
> pass CI.
>
> The branch you can use is 'next' (or 'master' if you need more stable
> stage).
> Other branches are used for development purposes and other internal needs.
>

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-

  reply	other threads:[~2022-11-25  8:05 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 [this message]
2022-11-25  8:30     ` Anton Mikanovich
2022-11-25  8:41       ` Roberto A. Foglietta
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='CAJGKYO6_BZJMVcivK_wJdFqmmDH_=gku4NGk8Hw8uyrGSB5M6A@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