From: Philip Kaludercic <philipk@posteo.net>
To: Omar Polo <op@omarpolo.com>
Cc: "Timo Myyrä" <timo.myyra@bittivirhe.fi>, emacs-devel@gnu.org
Subject: Re: [elpa] New package: vc-got
Date: Tue, 31 Aug 2021 13:32:57 +0000 [thread overview]
Message-ID: <87czptoi2e.fsf@posteo.net> (raw)
In-Reply-To: <87zgsx7v08.fsf@omarpolo.com> (Omar Polo's message of "Tue, 31 Aug 2021 12:17:26 +0200")
Omar Polo <op@omarpolo.com> writes:
> The code can be found here:
>
> https://git.omarpolo.com/vc-got
>
> or here as a mirror:
>
> https://github.com/omar-polo/vc-got
>
> and I've just tagged the 1.0 release.
Which of the two URLs are preferred?
> Regarding the code: I've discovered vc-do-command too late and rolled my
> own vc-got--call in the meantime. I do intend to make more use of the
> existing vc interface in future versions.
Would you want to update the project before it is added to ELPA? I might
also be able to find some time to comment on it if you are interested
(I too released a vc package (vc-backup) just a short while ago, so I
might be able to give some input of value).
> Talking about updates, one thing that I'm not sure is how to handle
> them: if tomorrow I'll release a v1.1 I do have to ping emacs-devel,
> right?
Not necessarily. The ELPA package specification can also contain an
:auto-sync attribute, indicating that the ELPA server will regularly
check for new updates (update-commits are identified by bumping the
version tag in the package header). If you can ensure that all
contributors have signed the copyright assignment and can maintain basic
repository hygiene, the packages can be updated manually too.
--
Philip Kaludercic
next prev parent reply other threads:[~2021-08-31 13:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 10:17 [elpa] New package: vc-got Omar Polo
2021-08-31 13:10 ` Eli Zaretskii
2021-08-31 13:31 ` Dmitry Gutov
2021-08-31 13:41 ` Eli Zaretskii
2021-08-31 13:46 ` Dmitry Gutov
2021-08-31 13:47 ` Eli Zaretskii
2021-08-31 13:55 ` Dmitry Gutov
2021-08-31 14:00 ` Eli Zaretskii
2021-08-31 14:02 ` Dmitry Gutov
2021-08-31 14:07 ` Eli Zaretskii
2021-08-31 14:08 ` Eli Zaretskii
2021-08-31 14:21 ` Stefan Kangas
2021-08-31 15:37 ` Eli Zaretskii
2021-10-17 4:57 ` Jean Louis
2021-10-17 6:21 ` Eli Zaretskii
2021-10-17 7:33 ` Jean Louis
2021-10-17 10:02 ` Eli Zaretskii
2021-10-17 10:13 ` Omar Polo
2021-08-31 14:00 ` Omar Polo
2021-08-31 14:34 ` Dmitry Gutov
2021-08-31 14:38 ` Omar Polo
2021-08-31 15:38 ` Eli Zaretskii
2021-08-31 14:44 ` Dmitry Gutov
2021-08-31 15:40 ` Eli Zaretskii
2021-08-31 13:32 ` Philip Kaludercic [this message]
2021-08-31 13:59 ` Omar Polo
2021-08-31 16:54 ` Philip Kaludercic
2021-09-09 15:50 ` Philip Kaludercic
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=87czptoi2e.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=op@omarpolo.com \
--cc=timo.myyra@bittivirhe.fi \
/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.