On Tue, Oct 24, 2023 at 02:25:06PM +0200, Christian Marangi wrote:
> On Tue, Oct 24, 2023 at 02:21:35PM +0200, Bjørn Mork wrote:
> > Christian Marangi writes:
> >
> > > Anyway I have also found this [1]... if it does actually works, it might
> > > be
> > > THE solution to our specific problem.
The sender domain has a DMARC Reject/Quarantine policy which disallows
sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped
automatically by the mailing list software.--- Begin Message ---
Hi, Bill,
I have a couple of
W dniu 23.10.2023 o 08:43, Linus Walleij pisze:
> This resurrects the support for IXP4xx using device tree
> rather than the old (deleted) board files. The final pieces
> of IXP4xx board files were deleted in Linux v5.19.
>
> Ext4 root filesystems on CF and USB are supported by the
> default
On Tue, 24 Oct 2023 at 17:46, Philip Prindeville
wrote:
>
> Hi,
>
> I'm seeing the following:
>
> https://github.com/openwrt/packages/actions/runs/6621741418/job/17986176198?pr=22362
>
> Specifically:
>
> mips-openwrt-linux-musl-gcc -shared -o libcligen.so.6.4 cligen_object.o
> cligen_callback.o
Hi,
I'm seeing the following:
https://github.com/openwrt/packages/actions/runs/6621741418/job/17986176198?pr=22362
Specifically:
mips-openwrt-linux-musl-gcc -shared -o libcligen.so.6.4 cligen_object.o
cligen_callback.o cligen_parsetree.o cligen_pt_head.o cligen_handle.o
cligen_cv.o
On Tue, Oct 24, 2023 at 02:21:35PM +0200, Bjørn Mork wrote:
> Christian Marangi writes:
>
> > Anyway I have also found this [1]... if it does actually works, it might be
> > THE solution to our specific problem. Wonder if someone can test it on a
> > sample repository.
> >
> > [1]
Christian Marangi writes:
> Anyway I have also found this [1]... if it does actually works, it might be
> THE solution to our specific problem. Wonder if someone can test it on a
> sample repository.
>
> [1] https://devblogs.microsoft.com/oldnewthing/20190919-00/?p=102904
Nice! Seems to work.
On Tue, Oct 24, 2023 at 01:40:22PM +0200, Bjørn Mork wrote:
> Ack on the broken history problem.
>
> I don't think it's necessary to keep two separate histories though. The
> main issue is the periodical removal of files keeping parts of history,
> resulting in an increasing number of file names
Ack on the broken history problem.
I don't think it's necessary to keep two separate histories though. The
main issue is the periodical removal of files keeping parts of history,
resulting in an increasing number of file names to follow for the
complete history.
Doing
git mv config-5.15
