From: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
To: Gustavo Padovan <gus@collabora.com>
Cc: linuxtv-ci@linuxtv.org,
"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>,
Denys Fedoryshchenko <denys.f@collabora.com>
Subject: Re: linux-media checkout failing for KernelCI
Date: Sat, 18 May 2024 00:40:03 +0300 [thread overview]
Message-ID: <78fd3f63760c0670cee4a8a4ac99a91a2b62706f.camel@nuclearcat.com> (raw)
In-Reply-To: <8edccc0b-d71a-b6ec-392f-3946f768db05@collabora.com>
On Fri, 2024-05-17 at 12:57 -0400, Gustavo Padovan wrote:
>
>
> On 5/17/24 11:29, Guenter Roeck wrote:
> > On Fri, May 17, 2024 at 6:41 AM Gustavo Padovan <gus@collabora.com>
> > wrote:
> > >
> > > Hi Media maintainers,
> > >
> > > We are struggling to use the media tree, in the same way we
> > > usually
> > > virtually all other trees in KernelCI. The following commands
> > > gives
> > > KernelCI a fatal error.
> > >
> > > git clone
> > > git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> > > cd linux
> > > git remote add media https://git.linuxtv.org/media_tree.git
> > > git remote update media
> > > git fetch --tags https://git.linuxtv.org/media_tree.git
> > Why not "git fetch --tags media" instead of the last two commands ?
> > That is working for me, and it is what I always use when fetching
> > remote repositories.
>
> Hmm. Maybe we were just being newbies with the way KernelCI does it.
> :)
Actually, the problem is that this "magical sequence" in the legacy
code was written years ago, and git blame gives incorrect results, so i
can't ask author "why?".
It’s a sort of "Chesterton's Fence" in the legacy library.
prev parent reply other threads:[~2024-05-17 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 13:41 linux-media checkout failing for KernelCI Gustavo Padovan
2024-05-17 13:45 ` Gustavo Padovan
2024-05-17 18:56 ` Mauro Carvalho Chehab
2024-05-17 19:46 ` Mauro Carvalho Chehab
2024-05-17 15:29 ` Guenter Roeck
2024-05-17 16:57 ` Gustavo Padovan
2024-05-17 21:40 ` Denys Fedoryshchenko [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=78fd3f63760c0670cee4a8a4ac99a91a2b62706f.camel@nuclearcat.com \
--to=nuclearcat@nuclearcat.com \
--cc=denys.f@collabora.com \
--cc=gus@collabora.com \
--cc=kernelci@lists.linux.dev \
--cc=linuxtv-ci@linuxtv.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).