Re: Unexpected behavior with :/<text> references

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

Subject: Re: Unexpected behavior with :/<text> references
From: William Chargin <wchargin@xxxxxxxxx>
Date: Mon, 9 Jul 2018 13:52:07 -0700
Cc: git@xxxxxxxxxxxxxxx
In-reply-to: <20180709180804.GA6134@sigill.intra.peff.net>
References: <CAFW+GMBLeLyJjJPaEXkyQ5fJ=L4q4vQ=26wjZ+n07ZvSaTaCUg@mail.gmail.com> <CAFW+GMAnkLYReotwRvbVt9iPqmuq_8WMc1sck4Jkj_fyafVm3w@mail.gmail.com> <20180709180804.GA6134@sigill.intra.peff.net>

Yep, I agree with your analysis. I'd be happy to test and commit this,
probably later today.

Thanks for your input, and for the patch!

Best,
WC

References:
- Unexpected behavior with :/<text> references
  - From: William Chargin
- Re: Unexpected behavior with :/<text> references
  - From: William Chargin
- Re: Unexpected behavior with :/<text> references
  - From: Jeff King

Prev by Date: [PATCH v2 6/6] commit-graph: add repo arg to graph readers
Next by Date: Re: [PATCH v3 16/20] range-diff --dual-color: work around bogus white-space warning
Previous by thread: Re: Unexpected behavior with :/<text> references
Next by thread: [PATCH 1/4] ref-filter: add info_source to valid_atom
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux