[gnuastro-devel] [task #14340] Defining arbitrary variable and its value in FITS headers

[Mohammad Akhlaghi]

Follow-up Comment #3, task #14340 (project gnuastro):

Boud posted the following message to this task but directory to the
gnuastro-devel mailing list
<http://lists.gnu.org/archive/html/gnuastro-devel/2017-01/msg00075.html>. So I
am also sending it here for the record. 

It can happen that we mistkanely reply to the mail instead of following the
link and posting the reply on Savannah. The categorization offered by Savannah
makes navigating the discussions here much more easier than a mailing list. So
in order to not miss any replys/comments in the future, I have updated the
settings of the gnuastro-devel mailing list. From now on, all direct mails to
that list will be rejected and an informative reply will be sent back
describing the recommended way to post a reply/comment. Thank you very much
Boud for bringing up this issue ;-).



Boud's message
--------------

In case gnuastro people don't know it: there's a fitsbits@ discussion
list where it might be worth coordinating some of these sorts of
questions:

https://listmgr.nrao.edu/mailman/listinfo/fitsbits

One of the recurring themes on that list is how to continue updating
FITS standards to follow or precede what really gets used in
astronomical FITS files, and to encourage people to implement the
standards. If gnuastro becomes widely used, then it may lead to
new de facto standards - so some coordination now at an early stage
might be useful.

Cheers
Boud

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/task/?14340>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/