On Thu, Oct 19, 2023, at 8:24 AM, Martin Simmons wrote: > 28bbfcdc0ed54d5498e82a773e3bf2ed100a9c7c is the commit for the Release-13.0.3 > tag, not the "most recent commit" for either bxattr_freebsd.c or the > repository as a whole, so I think that is where the misunderstanding started. > > c0e27eca4f29dfcc000b2156094b867e995a2f64 was the first attempt to fix it, but > it was then fixed again in 111333a97b10ce620c5b5bcf290980aaf454d922, which is > currently the most recent commit of bxattr_freebsd.c. > > __Martin
Thank you. Eric: this is no longer an issue. It was confusion on my part because I was trying to find the commit in order to apply the patches to the FreeBSD port. Knowing the commit id is useful for packagers in cases where the patch has not yet shipped in a release. Thank you. _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
