gnuastro-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[gnuastro-devel] [task #14007] Automatically generate ChangeLog from com


From: Mohammad Akhlaghi
Subject: [gnuastro-devel] [task #14007] Automatically generate ChangeLog from commit history
Date: Fri, 27 May 2016 03:41:24 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0

URL:
  <http://savannah.gnu.org/task/?14007>

                 Summary: Automatically generate ChangeLog from commit history
                 Project: GNU Astronomy Utilities
            Submitted by: makhlaghi
            Submitted on: Fri 27 May 2016 12:41:22 PM JST
         Should Start On: Fri 27 May 2016 12:00:00 AM JST
   Should be Finished on: Fri 27 May 2016 12:00:00 AM JST
                Category: Development
                Priority: 5 - Normal
              Item Group: Enhancement
                  Status: Postponed
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00

    _______________________________________________________

Details:

Following the discussion in task #13779, we have dropped updating of the
ChangeLog as part of Gnuastro's development. However, as discussed there, it
is possible to generate the ChangeLog automatically from the commit history
using tools in Gnulib. This can be done once on every release and in the
bootstrap process. 

In between releases, the only way to get the source is cloning the Git
repository, so a ChangeLog is mostly irrelevant in such cases, since Git has
many highly customizable tools for viewing the changes.








    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]