Hi. Thanks for your prompt attention. Again, sorry for my
contribution to an annoying situation.
Jonathan Nieder writes ("Re: git introduces new hazardous working-tree-encoding
attribute"):
> Ian Jackson wrote:
> > Subject: git introduces new hazardous working-tree-encoding attribute
>
> This title doesn't describe a bug. On first reading, I thought you
> were saying that some working-tree-encoding related feature was
> behaving incorrectly, but it doesn't appear to be so. (I was trying
> to understand so that I could forward this report upstream.)
Sorry about that.
> Happy to add a Breaks. Do you know what version of dgit will have the
> fix?
5.1. I suggest
Breaks: dgit (<< 5.1~)
5.1 doesn't exist yet but fixing this issue is very high up on my
list. Expect it in the next few days. dgit 5.0 has not yet migrated
and was due to do so on about Sunday. Because 5.0 has a lot of other
changes I don't want to bring that forward, but I will upload 5.1 with
a higher urgency, so that the migration date is not delayed either.
Much of the rest of what you write is perhaps more relevant to 851679
so I'll answer it there.
Thanks,
Ian.
--
Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
