unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Vasilij Schneidermann <mail@vasilij.de>
Cc: 43775@debbugs.gnu.org, larsi@gnus.org, philipk@posteo.net,
	bugs@gnu.support, rms@gnu.org
Subject: bug#43775: 28.0.50; Feature request: to include EPUB reading into main Emacs
Date: Mon, 12 Oct 2020 17:55:22 +0300	[thread overview]
Message-ID: <83y2kb3351.fsf@gnu.org> (raw)
In-Reply-To: <20201012063636.GB56409@odonien.localdomain> (message from Vasilij Schneidermann on Mon, 12 Oct 2020 08:36:36 +0200)

> Date: Mon, 12 Oct 2020 08:36:36 +0200
> From: Vasilij Schneidermann <mail@vasilij.de>
> Cc: 43775@debbugs.gnu.org, "Philip K." <philipk@posteo.net>,
>  Richard Stallman <rms@gnu.org>, Jean Louis <bugs@gnu.support>
> 
> > Yes, sounds like a good idea.
> 
> Great, now how do I get there?  Presumably I'll need write access and
> someone to guide me into the exact Git workflow used there?

To get write access, create a user on Savannah, and then request to
make that use a member of the Emacs project.  I will then approve you,
and that will give you write access to the Git repository.

For the Git worklfow, I'm not sure what you mean.  You are going to
add code to an existing file, right?  If so, just post the patches for
review, and when all the comments are addressed, push the changeset to
the master branch.

Some details are in CONTRIBUTE and in admin/notes/git-workflow, but
I'm not sure you need that.  In general, new features are always
pushed to the master branch, and bugfixes either to the release branch
or the master branch; the release branch is then merged periodically
onto master.  If you are not sure about something, just ask.

TIA





  reply	other threads:[~2020-10-12 14:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-03  9:03 bug#43775: 28.0.50; Feature request: to include EPUB reading into doc-view Jean Louis
     [not found] ` <VI1PR06MB4526E1B8D23CC152E879499C960E0@VI1PR06MB4526.eurprd06.prod.outlook.com>
2020-10-03 10:26   ` bug#43775: Sv: " Jean Louis
2020-10-03 11:30 ` Philip K.
2020-10-04  3:44   ` Richard Stallman
2020-10-04  4:40     ` bug#43775: 28.0.50; Feature request: to include EPUB reading into main Emacs Jean Louis
2020-10-04  5:48       ` Vasilij Schneidermann
2020-10-05  3:15         ` Richard Stallman
2020-10-05  4:12           ` Jean Louis
2020-10-05  4:22           ` Vasilij Schneidermann
2020-10-05  5:17             ` Jean Louis
2020-10-06  2:30             ` Richard Stallman
     [not found]             ` <E1kPco3-000841-JM@fencepost.gnu.org>
2020-10-07 17:47               ` Vasilij Schneidermann
2020-10-05  7:53         ` Lars Ingebrigtsen
2020-10-05  8:52           ` Arthur Miller
2020-10-05 11:36             ` Vasilij Schneidermann
2020-10-05 11:32           ` Vasilij Schneidermann
2020-10-06  1:31             ` Lars Ingebrigtsen
2020-10-07 17:50               ` Vasilij Schneidermann
2020-10-09  4:16                 ` Lars Ingebrigtsen
2020-10-12  6:36                   ` Vasilij Schneidermann
2020-10-12 14:55                     ` Eli Zaretskii [this message]
2020-10-04  7:22     ` bug#43775: 28.0.50; Feature request: to include EPUB reading into doc-view Eli Zaretskii
2022-04-23 14:50 ` Lars Ingebrigtsen

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=83y2kb3351.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=43775@debbugs.gnu.org \
    --cc=bugs@gnu.support \
    --cc=larsi@gnus.org \
    --cc=mail@vasilij.de \
    --cc=philipk@posteo.net \
    --cc=rms@gnu.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.
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).