public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Cedric Hombourger <Cedric_Hombourger@mentor.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH v4 0/1] dpkg-base: resolve DL_DIR in do_adjust_git
Date: Mon, 21 Feb 2022 12:25:38 +0300	[thread overview]
Message-ID: <dd3e9622-1312-fff1-1c90-f7c5f0b16124@ilbers.de> (raw)
In-Reply-To: <20220209081244.814-1-Cedric_Hombourger@mentor.com>

9.02.22 11:12, Cedric Hombourger wrote:
> Changes since v3:
>    The path placed in .git/objects/info/alternates shall be relative,
>    we should resolve git symbolic links only when comparing them
>
> v3 changes:
>    fix subject line
>
> v2 changes:
>    found actual root cause. instead of catching FileExistsError, we
>    should instead resolve symbolic links and compare them. In the
>    event when they do not match, the previous symbolic link should
>    be re-created.
>
> Cedric Hombourger (1):
>    dpkg-base: resolve DL_DIR in do_adjust_git
>
>   meta/classes/dpkg-base.bbclass | 10 +++++++---
>   1 file changed, 7 insertions(+), 3 deletions(-)
>
Applied to next, thanks.


  parent reply	other threads:[~2022-02-21  9:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 13:41 [PATCH] dpkg-base: cope with race around check/creation of .git-downloads symlink Cedric Hombourger
2022-02-02  7:05 ` Jan Kiszka
2022-02-04  8:34   ` Cedric Hombourger
2022-02-04 10:50   ` [[PATCH v2]] dpkg-base: resolve DL_DIR in do_adjust_git Cedric Hombourger
2022-02-04 10:54   ` [PATCH v3] " Cedric Hombourger
2022-02-04 11:04     ` Jan Kiszka
2022-02-04 12:45       ` Cedric Hombourger
2022-02-09  8:12         ` [PATCH v4 0/1] " Cedric Hombourger
2022-02-09  8:12           ` [PATCH v4 1/1] " Cedric Hombourger
2022-02-21  9:25           ` Anton Mikanovich [this message]
2022-02-04 12:30     ` [PATCH v3] " Henning Schild
2022-02-04 12:43       ` Jan Kiszka
2023-02-16 12:57       ` Henning Schild

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=dd3e9622-1312-fff1-1c90-f7c5f0b16124@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=Cedric_Hombourger@mentor.com \
    --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