emacs-bug-tracker
[Top][All Lists]
Advanced

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

[debbugs-tracker] bug#22506: closed (make change-history now doesn't wor


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#22506: closed (make change-history now doesn't work at all)
Date: Mon, 01 Feb 2016 07:42:02 +0000

Your message dated Sun, 31 Jan 2016 23:41:42 -0800
with message-id <address@hidden>
and subject line Re: bug#22506: make change-history now doesn't work at all
has caused the debbugs.gnu.org bug report #22506,
regarding make change-history now doesn't work at all
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
22506: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22506
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: make change-history now doesn't work at all Date: Sun, 31 Jan 2016 14:23:09 -0500 User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
Package: emacs
Version: 25.0.90

I don't know how y'all plan to address the issue of running make
change-history on the release branch (bug#21998), but now it doesn't
work on either emacs-25 or master. On both branches,
change-history-nocommit fails with "fatal: Invalid revision range". Eg:

  GEN      ChangeLog
fatal: Invalid revision range
3f43da09956b663d92f578e41bcacb8742bb6bba..0156b79ea8fd473c550abdb8d3e3b4eacaaab289
gitlog-to-changelog: error closing pipe from git log --log-size
'--pretty=format:%H:%ct  %an  <%ae>%n%n%B'
3f43da09956b663d92f578e41bcacb8742bb6bba..0156b79ea8fd473c550abdb8d3e3b4eacaaab289
make[1]: *** [ChangeLog] Error 128



--- End Message ---
--- Begin Message --- Subject: Re: bug#22506: make change-history now doesn't work at all Date: Sun, 31 Jan 2016 23:41:42 -0800 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 I assume this particular bug (the one that blocks a release) has been fixed, so I'll close the bug report. If I haven't actually fixed it please feel free to reopen it. We do have the more-general problem that ChangeLog maintenance is a pain, but that should be a different bug as it does not block a release.


--- End Message ---

reply via email to

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