From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: 36440@debbugs.gnu.org
Subject: [bug#36440] [PATCH] Add FreeCAD
Date: Fri, 19 Jul 2019 22:40:50 +0200 [thread overview]
Message-ID: <9019fc17-077b-c1f0-ebc4-9b20bb6e292d@web.de> (raw)
In-Reply-To: <CAKf5CqXqHCTDEwisd6Y2R79bF5350pbpE4s_Hq00GSJ12s2-cg@mail.gmail.com>
Is there a reason why you build every package from a commit of the
master branch instead of using the stable releases? I think at least
FreeCAD releases often enough, in the mean time the released version 0.18.3.
Do you have the patches also in some public git repo (Github, Gitlab etc.)?
~Jonathan
next prev parent reply other threads:[~2019-07-19 20:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-30 2:39 [bug#36440] [PATCH] Add FreeCAD John Soo
2019-07-02 7:06 ` Björn Höfling
[not found] ` <CAKf5CqXWCGX4y3nJ3KeV2=fxrR2XA8-E-g1=i1zdQqEv-h6XcQ@mail.gmail.com>
2019-07-08 1:17 ` [bug#36440] Fwd: " John Soo
2019-07-10 14:02 ` John Soo
2019-07-19 20:40 ` Jonathan Brielmaier [this message]
2019-07-22 13:41 ` [bug#36440] Source commit, minor version difference, channel John Soo
2019-07-22 14:11 ` [bug#36440] [PATCH] Add FreeCAD Björn Höfling
2019-07-22 17:57 ` Jonathan Brielmaier
2019-07-23 16:25 ` John Soo
2019-07-23 16:29 ` John Soo
2019-07-24 21:59 ` Ricardo Wurmus
2019-07-24 7:52 ` Jonathan Brielmaier
2019-07-24 19:46 ` John Soo
2019-07-24 21:51 ` Ricardo Wurmus
2019-07-30 12:24 ` Paul Garlick
2019-09-02 13:23 ` Ludovic Courtès
2019-09-02 13:33 ` John Soo
2019-09-03 5:22 ` John Soo
2019-09-03 15:10 ` John Soo
2019-09-03 19:45 ` Paul Garlick
2019-09-04 5:44 ` John Soo
2019-09-04 5:47 ` John Soo
2019-09-04 6:47 ` John Soo
2019-09-11 14:19 ` John Soo
2019-09-22 7:09 ` bug#36440: " Björn Höfling
2019-09-22 16:00 ` [bug#36440] " John Soo
2019-09-22 17:50 ` Björn Höfling
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=9019fc17-077b-c1f0-ebc4-9b20bb6e292d@web.de \
--to=jonathan.brielmaier@web.de \
--cc=36440@debbugs.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 external index
https://git.savannah.gnu.org/cgit/guix.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.