On Sat, Jan 13, 2024 at 3:56 PM Nathan Hartman
wrote:
> Pros: Future-proofing against the real and perceived brokenness of any
> hash types.
>
I meant to write:
Pros: Future-proofing against the real and perceived brokenness of any hash
types, or the deprecation and later removal of their
On Fri, Jan 12, 2024 at 3:51 PM Johan Corveleyn wrote:
> On Fri, Jan 12, 2024 at 12:37 PM Daniel Shahaf
> wrote:
> ...
> > Procedurally, the long hiatus is counterproductive. Neither kfogel nor
> > I had the context in our heads, and the cache misses took their toll in
> > tuits and in
Den fre 12 jan. 2024 kl 12:02 skrev Daniel Shahaf :
> I think it should be clear to members of our community how to access our
> Collective Memory (= the list archives) in the preferred form for
> reading, to borrow ALv2's definition of "Source". I would expect that
> to be self-evident from
Den lör 13 jan. 2024 kl 00:50 skrev Johan Corveleyn :
> On Fri, Jan 12, 2024 at 12:37 PM Daniel Shahaf
> wrote:
> ...
> > Procedurally, the long hiatus is counterproductive. Neither kfogel nor
> > I had the context in our heads, and the cache misses took their toll in
> > tuits and in wallclock
Den ons 10 jan. 2024 kl 10:45 skrev Stefan Sperling :
> On Wed, Jan 10, 2024 at 09:44:51AM +0100, Johan Corveleyn wrote:
> > Interesting discussion. I agree it should at least be documented, and
> > perhaps be made a bit more clear from the output of 'revert' (but not
> > sure how far we can go
Den fre 5 jan. 2024 kl 08:45 skrev Daniel Sahlberg <
daniel.l.sahlb...@gmail.com>:
> Hi,
>
> When researching the spurious revert messages reported by Vincent Lefevre
> [1], I was looking at the code in svn_io__is_finfo_read_only() and
> svn_io_is_file_executable(). It gets the current UID and
6 matches
Mail list logo
