From: Eli Zaretskii <eliz@gnu.org>
To: Pankaj Jangid <pankaj@codeisgreat.org>
Cc: emacs-devel@gnu.org
Subject: Re: Why BBDB package manual is empty?
Date: Sat, 21 May 2022 12:31:32 +0300 [thread overview]
Message-ID: <83wnef8c5n.fsf@gnu.org> (raw)
In-Reply-To: <87fsl36y8k.fsf@codeisgreat.org> (message from Pankaj Jangid on Sat, 21 May 2022 14:47:31 +0530)
> From: Pankaj Jangid <pankaj@codeisgreat.org>
> Cc: emacs-devel@gnu.org
> Date: Sat, 21 May 2022 14:47:31 +0530
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Are there any technical difficulties of shipping BBDB manual with the
> >> package? Like licensing or other issues.
> >>
> >> Right now I can see a manual with blank "First Chapter". That’s it.
> >
> > It will have to be written before it can be shipped. What you see is
> > all that was written. There's nothing more in the Texinfo source of
> > that manual.
>
> Okay. I thought some licensing and copyright issue. Because I can see a
> manual for version 2.35 on SourceForge -
> http://bbdb.sourceforge.net/bbdb.html
maybe it was, I don't know all the history of this package on ELPA.
next prev parent reply other threads:[~2022-05-21 9:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 3:24 Why BBDB package manual is empty? Pankaj Jangid
2022-05-21 5:46 ` Eli Zaretskii
2022-05-21 9:17 ` Pankaj Jangid
2022-05-21 9:31 ` Eli Zaretskii [this message]
2022-05-22 1:33 ` Michael Heerdegen
2022-05-22 6:25 ` Pankaj Jangid
2022-05-22 23:15 ` Roland Winkler
2022-05-22 23:20 ` Stefan Monnier
2022-05-23 7:42 ` Juri Linkov
2022-05-23 1:58 ` Michael Heerdegen
2022-05-21 6:31 ` Michael Heerdegen
2022-05-21 9:37 ` Pankaj Jangid
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=83wnef8c5n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=pankaj@codeisgreat.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).