On 10/20/2016 06:08 PM, Bruno Haible wrote:
Paul, since you say that HP-UX is still living on but none of us has access to
a HP-UX machine, I wrote "HP-UX 11.31 is very rarely tested."
Thanks, that sounds OK. At this point we only "test" HP-UX indirectly,
when a downstream package is built on
On 10/21/2016 03:17 PM, Eric Blake wrote:
> On 10/21/2016 02:39 PM, Reuben Thomas wrote:
>
>> hey seem only to be tags: git fsck --verbose says only for each error:
>>
>> Checking tag 68c0e85dba93471b4f7d450ae2e6139a56574549
>> error in tag 68c0e85dba93471b4f7d450ae2e6139a56574549: missingEmail:
On 10/21/2016 02:46 PM, Bruno Haible wrote:
> Eric Blake wrote:
>>> I get lots of "error in tag foo: missingEmail" errors, and an error exit
>>> code. I guess this is just a minor annoyance?
>>
>> Sounds like the tags were created in a much older version of git, and
>> that newer git complains abou
On 10/21/2016 02:39 PM, Reuben Thomas wrote:
> hey seem only to be tags: git fsck --verbose says only for each error:
>
> Checking tag 68c0e85dba93471b4f7d450ae2e6139a56574549
> error in tag 68c0e85dba93471b4f7d450ae2e6139a56574549: missingEmail:
> invalid author/committer line - missing email
>
Eric Blake wrote:
> > I get lots of "error in tag foo: missingEmail" errors, and an error exit
> > code. I guess this is just a minor annoyance?
>
> Sounds like the tags were created in a much older version of git, and
> that newer git complains about what the older version was able to
> create.
On 21 October 2016 at 20:32, Eric Blake wrote:
> On 10/21/2016 02:25 PM, Paul Eggert wrote:
> > On 10/21/2016 12:18 PM, Reuben Thomas wrote:
> >> fsckobjects = true
> >>
> >> I commented it out, and the checkout succeeded. If I then run "git
> >> fsck", I get lots of "error in tag foo
On 10/21/2016 02:25 PM, Paul Eggert wrote:
> On 10/21/2016 12:18 PM, Reuben Thomas wrote:
>> fsckobjects = true
>>
>> I commented it out, and the checkout succeeded. If I then run "git
>> fsck", I get lots of "error in tag foo: missingEmail" errors, and an
>> error exit code. I guess th
On 10/21/2016 02:18 PM, Reuben Thomas wrote:
>
> I had the following setting in my .gitconfig:
>
> [transfer]
> # for $deity's sake, check that anything we're getting is complete and sane
> on a regular basis
> # See
> https://groups.google.com/forum/m/#!topic/binary-transparency/f-BI4o8HZW0
>
On 10/21/2016 12:18 PM, Reuben Thomas wrote:
fsckobjects = true
I commented it out, and the checkout succeeded. If I then run "git
fsck", I get lots of "error in tag foo: missingEmail" errors, and an
error exit code. I guess this is just a minor annoyance?
More like a major annoya
On 21 October 2016 at 20:11, Paul Eggert wrote:
> On 10/21/2016 12:04 PM, Reuben Thomas wrote:
>
>> error: object ac0afbe494560392efad871a77f18c0aaa4d504a: missingEmail:
>> invalid author/committer line - missing email
>>
>
> I am not observing that problem, also with Git 2.7.4:
>
> $ git clone g
On 10/21/2016 12:04 PM, Reuben Thomas wrote:
error: object ac0afbe494560392efad871a77f18c0aaa4d504a: missingEmail:
invalid author/committer line - missing email
I am not observing that problem, also with Git 2.7.4:
$ git clone git://git.savannah.gnu.org/findutils.git tmp
Cloning into 'tmp'...
On 21 October 2016 at 19:59, Eric Blake wrote:
> [adding James and findutils]
>
>
> Gnulib is currently just a distribution point; the upstream template was
> written by James Youngman for findutils (see
> findutils.git/lib/regexprops.c). But I suspect patches would be
> welcome, if you'd like t
[adding James and findutils]
On 10/21/2016 01:43 PM, Reuben Thomas wrote:
> On 21 October 2016 at 14:46, Reuben Thomas wrote:
>
>> On 21 October 2016 at 14:25, Eric Blake wrote:
>>
>>>
>>> In fact, such documentation already exists, and IS used in other GNU
>>> manuals: at least findutils and m
On 21 October 2016 at 14:46, Reuben Thomas wrote:
> On 21 October 2016 at 14:25, Eric Blake wrote:
>
>>
>> In fact, such documentation already exists, and IS used in other GNU
>> manuals: at least findutils and m4 use the regexprops-generic module,
>> which generates the gnulib file doc/regexpro
On 21 October 2016 at 14:25, Eric Blake wrote:
>
> In fact, such documentation already exists, and IS used in other GNU
> manuals: at least findutils and m4 use the regexprops-generic module,
> which generates the gnulib file doc/regexprops-generic.texi as a
> human-readable user description of a
On 10/21/2016 07:52 AM, Reuben Thomas wrote:
> Since the regexp code is widely used, with mechanically-defined syntax
> variants, in GNU grep, GNU sed etc., it would seem possible to have a
> mechanically-generated manual, which takes a set of GNU regexp syntax
> flags, as taken by re_set_syntax, a
I just noticed while working on Emacs's whitespace.el that Emacs’s syntax
coloring does not color the sequence “\\{” specially in a string, though it
recognises other regexp metacharacters such as “\\(”.
I looked in the Emacs manuals, and found no mention of braces as a special
character, despite
17 matches
Mail list logo
