From: Ihor Radchenko <yantar92@posteo.net>
To: Bastien Guerry <bzg@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
Jeremie Juste <jeremiejuste@gmail.com>,
emacs-devel@gnu.org
Subject: Re: branch main created (now ffb30cd7373)
Date: Sun, 04 Dec 2022 05:33:27 +0000 [thread overview]
Message-ID: <87h6ybka1k.fsf@localhost> (raw)
In-Reply-To: <875yer8o3z.fsf@gnu.org>
Bastien Guerry <bzg@gnu.org> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> It looks like someone has pushed a 'main' branch to the Emacs Git
>> repository, and that branch looks like it belongs to the Org Git
>> repository?
>
> I didn't push anything since Org 9.6, I'll see what happened here and
> try to fix it later (>7pm CET), unless Kyle or Ihor fix it before.
From git log on Emacs main vs. Org main, it looks like Jeremie messed
something when pushing his patch upstream. See
https://orgmode.org/list/87lenob0ql.fsf@gmail.com
Jeremie, it looks like your upstream git configuration is off. Your
commit did not land onto Org git repo upstream and instead messed up the
main Emacs repo. If you need any help with git setup, please let us know.
Eli, I think you can simply remote this erroneously pushed branch.
Jeremie can push his commit to Org repo after fixing the problem with
local git setup.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2022-12-04 5:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 6:31 branch main created (now ffb30cd7373) Eli Zaretskii
2022-12-04 10:22 ` Bastien Guerry
2022-12-04 5:33 ` Ihor Radchenko [this message]
2022-12-04 11:44 ` Eli Zaretskii
2022-12-04 22:06 ` Jeremie Juste
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6ybka1k.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bzg@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jeremiejuste@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).