Re: fileflags

Ryan Carsten Schmidt via rsync <[email protected]> Wed, 20 May 2026 12:41:35 -0500
Newsgroups gmane.network.rsync.general
Message-ID <[email protected]>
--===============8472027771536594943==
Content-Type: multipart/alternative; boundary=Apple-Mail-98435402-F196-4B28-B28E-6778CEFDD80C
Content-Transfer-Encoding: 7bit


--Apple-Mail-98435402-F196-4B28-B28E-6778CEFDD80C
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

On May 19, 2026, at 01:39, Andrew Tridgell via rsync wrote:
>=20
> One of the problems with the patches archive was we had no idea if
> anyone was using it, so its purpose as a staging area for changes to
> go into the main release didn't work very well.
> Now I know FreeBSD included it I could create a PR for it to go into a
> future release as a standard feature.

MacPorts has been using the fileflags.diff patch since 2008. It was added to=
 resolve this bug report:

https://trac.macports.org/ticket/15472

We started using crtimes.diff at the same time, until it was merged into the=
 main sources in rsync 3.2.3.

We also used the hfscompression.diff patch since 2012 to resolve this featur=
e request:

https://trac.macports.org/ticket/35514

but rsync 3.1.3 broke that. I recall discussing that matter with rsync devel=
opers at that time. Reenabling this feature remains an open to-do for us:

https://trac.macports.org/ticket/60792

And had been for the rsync project as well until the repository was archived=
:

https://github.com/RsyncProject/rsync-patches/issues/1


--Apple-Mail-98435402-F196-4B28-B28E-6778CEFDD80C
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div dir=3D"ltr"></div><div dir=3D"ltr">On M=
ay 19, 2026, at 01:39, Andrew Tridgell via rsync wrote:</div><div dir=3D"ltr=
"><blockquote type=3D"cite"><br></blockquote></div><blockquote type=3D"cite"=
><div dir=3D"ltr"><span>One of the problems with the patches archive was we h=
ad no idea if</span><br><span>anyone was using it, so its purpose as a stagi=
ng area for changes to</span><br><span>go into the main release didn't work v=
ery well.</span><br><span>Now I know FreeBSD included it I could create a PR=
 for it to go into a</span><br><span>future release as a standard feature.</=
span></div></blockquote><br><div>MacPorts has been using the fileflags.diff p=
atch since 2008. It was added to resolve this bug report:</div><div><br></di=
v><div><a href=3D"https://trac.macports.org/ticket/15472">https://trac.macpo=
rts.org/ticket/15472</a></div><div><br></div><div>We started using crtimes.d=
iff at the same time, until it was merged into the main sources in rsync 3.2=
.3.</div><div><br></div><div>We also used the hfscompression.diff patch sinc=
e 2012 to resolve this feature request:</div><div><br></div><div><a href=3D"=
https://trac.macports.org/ticket/35514">https://trac.macports.org/ticket/355=
14</a></div><div><br></div><div>but rsync 3.1.3 broke that. I recall discuss=
ing that matter with rsync developers at that time. Reenabling this feature r=
emains an open to-do for us:</div><div><br></div><div><a href=3D"https://tra=
c.macports.org/ticket/60792">https://trac.macports.org/ticket/60792</a></div=
><div><br></div><div>And had been for the rsync project as well until&nbsp;<=
span style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">the repositor=
y was</span>&nbsp;archived:</div><div><br></div><div><a href=3D"https://gith=
ub.com/RsyncProject/rsync-patches/issues/1">https://github.com/RsyncProject/=
rsync-patches/issues/1</a></div><div><br></div></body></html>=

--Apple-Mail-98435402-F196-4B28-B28E-6778CEFDD80C--


--===============8472027771536594943==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

--===============8472027771536594943==--