From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14841] support/download/git fails with "fatal: No such remote 'origin'" due to incorrect check for origin remote
Date: Sat, 30 Jul 2022 19:55:28 +0000 [thread overview]
Message-ID: <bug-14841-163-WvYEUKghBb@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14841-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14841
Yann E. MORIN <yann.morin.1998@free.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|NEW |RESOLVED
--- Comment #3 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Hello,
We did not get feedback, or more explanations about your issue, and
there are two people that reported that the case you described did
in fact work as expected.
So we're clodsing this issue report. Feel free to reopen with more
information if you still have the issue.
Regards,
Yann E. MORIN.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-30 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 23:57 [Buildroot] [Bug 14841] New: support/download/git fails with "fatal: No such remote 'origin'" due to incorrect check for origin remote bugzilla
2022-06-10 23:59 ` [Buildroot] [Bug 14841] " bugzilla
2022-06-13 8:15 ` [Buildroot] [Bug 14841] New: " Edgar Bonet
2022-06-14 19:55 ` [Buildroot] [Bug 14841] " bugzilla
2022-07-30 19:55 ` bugzilla [this message]
2022-10-24 20:09 ` bugzilla
2022-10-24 20:10 ` bugzilla
2024-06-15 15:03 ` bugzilla
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=bug-14841-163-WvYEUKghBb@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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