From: Ihor Radchenko <yantar92@posteo.net>
To: "Juan Manuel Macías" <maciaschain@posteo.net>, Bastien <bzg@gnu.org>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: A question about local/experimental branches
Date: Sun, 25 Feb 2024 14:05:33 +0000 [thread overview]
Message-ID: <87h6hw1vwy.fsf@localhost> (raw)
In-Reply-To: <878r38hcq1.fsf@posteo.net>
Juan Manuel Macías <maciaschain@posteo.net> writes:
> I've noticed that the code for my implementation of the new
> 'inline-special-block' experimental element is growing. In addition, I
> introduce modifications and improvements daily. So I think it might be a
> good idea to make my local branch public, in case someone wants to try
> it or contribute to the project.
>
> My question is if there is any set of good practices to do this, or is
> it enough to publish the local branch 'as is'.
See https://orgmode.org/worg/org-contribute.html#orgfd0d3cb
You can just share the link to your branch.
I am not sure if experimental branches can go directly to our savannah,
like what Emacs does.
Bastien, WDYT?
P.S. Juan, I will need some time to review previous discussions on
inline special blocks before I can comment on your work in depth.
--
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:[~2024-02-25 14:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 13:53 A question about local/experimental branches Juan Manuel Macías
2024-02-25 14:05 ` Ihor Radchenko [this message]
2024-02-25 15:10 ` Juan Manuel Macías
2024-02-26 8:43 ` Bastien Guerry
2024-02-26 11:05 ` Org agenda view does not display correctly Naresh Gurbuxani
2024-02-26 11:18 ` Ihor Radchenko
2024-02-26 11:06 ` A question about local/experimental branches Ihor Radchenko
2024-02-26 13:03 ` Bastien Guerry
2024-02-27 9:57 ` Juan Manuel Macías
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=87h6hw1vwy.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=maciaschain@posteo.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.