Bruno Haible [EMAIL PROTECTED] wrote:
James Youngman wrote:
These days, I use a ChangeLog-format change message as my GIT commit
message, which solves most of the problem. It's still not that
convenient, sadly, because
(1) I have not yet taken the time to wrap Emacs' add-change-log-entry
the argz.m4 header checks to see if error_t is defined, but only does so by
including the argz.h header. if you try to build on a system that does
provide error_t, but not argz.h, the argz replacement module fails to build.
on glibc systems, error_t is defined in errno.h. perhaps the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Eric Blake on 2/7/2008 5:22 PM:
|
| 2008-02-07 Eric Blake [EMAIL PROTECTED]
|
| Quotearg part 3: add flag to control outer quote elision.
| * lib/quotearg.h (c_maybe_quoting_style): New style.
| (enum quoting_flags):
Simon Josefsson wrote:
From whom, please? I would like to acknowledge the original reporter.
Hi! It was Adam Strzelecki [EMAIL PROTECTED], in:
http://article.gmane.org/gmane.comp.gnu.gsasl.general/122
Thanks.
*** ChangeLog.orig 2008-02-13 00:22:06.0 +0100
--- ChangeLog
James Youngman wrote:
These days, I use a ChangeLog-format change message as my GIT commit
message, which solves most of the problem. It's still not that
convenient, sadly, because
(1) I have not yet taken the time to wrap Emacs' add-change-log-entry
so that it creates a new file for use
Bruno Haible [EMAIL PROTECTED] writes:
Hi Simon,
Hi! I received a patch for vasnprintf with rationale:
From whom, please? I would like to acknowledge the original reporter.
Hi! It was Adam Strzelecki [EMAIL PROTECTED], in:
http://article.gmane.org/gmane.comp.gnu.gsasl.general/122
-
[ Cc:ing bug-libtool, it's upstream for argz ]
Hi Mike,
* Mike Frysinger wrote on Wed, Feb 13, 2008 at 05:38:05AM CET:
the argz.m4 header checks to see if error_t is defined, but only does so by
including the argz.h header. if you try to build on a system that does
provide error_t, but not
On Feb 12, 2008 2:41 AM, Micah Cowan [EMAIL PROTECTED] wrote:
OTOH, a more difficult problem might be: how do you go about fixing
erroneous commit logs? In Subversion and CVS, this can be dealt with if
you have appropriate privileges; but in Mercurial at least (and probably
Git as well?), the
