On Wed, Dec 07, 2016 at 12:13:01PM -0500, Will Parsons wrote:
> On Tuesday, 6 Dec 2016 5:46 PM -0500, bch wrote:
> > I've got a collection of files who's apparently only change is the
> > EXECUTABLE bit set, but after a commit, they're still showing up in "f
> > chan"; I retried w/ a --sha1sum
On Dec 7, 2016 09:13, "Will Parsons" wrote:
On Tuesday, 6 Dec 2016 5:46 PM -0500, bch wrote:
> I've got a collection of files who's apparently only change is the
> EXECUTABLE bit set, but after a commit, they're still showing up in "f
> chan"; I retried w/ a --sha1sum
On Tuesday, 6 Dec 2016 5:46 PM -0500, bch wrote:
> I've got a collection of files who's apparently only change is the
> EXECUTABLE bit set, but after a commit, they're still showing up in "f
> chan"; I retried w/ a --sha1sum switch; still listed as changed
> (despite the new commit showing up in
On Dec 6, 2016 19:18, "Andy Bradford" wrote:
Thus said bch on Tue, 06 Dec 2016 14:46:23 -0800:
> I've got a collection of files who's apparently only change is the
> EXECUTABLE bit set, but after a commit, they're still showing up in "f
> chan"; I retried w/ a
Thus said bch on Tue, 06 Dec 2016 14:46:23 -0800:
> I've got a collection of files who's apparently only change is the
> EXECUTABLE bit set, but after a commit, they're still showing up in "f
> chan"; I retried w/ a --sha1sum switch; still listed as changed
> (despite the new commit
I've got a collection of files who's apparently only change is the
EXECUTABLE bit set, but after a commit, they're still showing up in "f
chan"; I retried w/ a --sha1sum switch; still listed as changed
(despite the new commit showing up in the "f timel"). touch(1) all the
affected files to bump
6 matches
Mail list logo