Date: Wed, 26 Nov 2025 11:48:43 +0200 From: Sulev-Madis Silber <freebsd-hackers-freebsd-org952@ketas.si.pri.ee> To: freebsd-hackers@freebsd.org Subject: =?US-ASCII?Q?Re=3A_=5BPATCH=5D_df=3A_correct_BLOCKSIZE_han?= =?US-ASCII?Q?dling_for_-k_to_use_1K-blocks_=28290710=29?= Message-ID: <6B77F3D4-C55D-4C63-9537-EBC151AFA35F@ketas.si.pri.ee> In-Reply-To: <CANCZdfprduu7SZ-aA2GC8ya1nLit_bcH2a8tV=ZQD1J6%2B2Q_2Q@mail.gmail.com> References: <CAEw80_2bA-NgE_XF0KVr55PSUDGEQTWGE7t9rpxOhykY1MsSvA@mail.gmail.com> <CANCZdfo9XbAKcgtSw953hpwc9jegzPhaVtfk7DtYTKdoHRnkUg@mail.gmail.com> <1789299192.176069.1764023439861@privateemail.com> <20251125082605.0cb9ab55a2c71a415b575c41@dec.sakura.ne.jp> <86h5ui7qd5.fsf@ltc.des.dev> <20251125214658.eb1e0cdf9df97601b9e28de9@dec.sakura.ne.jp> <774F9B09-B506-4F8E-B293-CE705F64B77A@ketas.si.pri.ee> <1497323956.336174.1764124966236@privateemail.com> <CANCZdfprduu7SZ-aA2GC8ya1nLit_bcH2a8tV=ZQD1J6%2B2Q_2Q@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
i did ( git diff --color sysutils/u-boot-master/ sysutils/u-boot-orangepi-zero-2w/ sysutils/atf-sun50i_h616/ ; git ls-files -o sysutils/u-boot-master/ sysutils/u-boot-orangepi-zero-2w/ sysutils/atf-sun50i_h616/ | xargs -n 1 git diff --color /dev/null ) | less -R i mean, just the sheer amount of manual work... an alternative is stashing stashpopping stashpushing headresetting messing whatever? i mean oneliner there and it's scripted better version does allow me to eyeball the changes and possibly submit the above change (uboot for h618 board) but it only works nicely from the top of tree i mean git does include many commands that work on untracked files on wd, so why not have special flag to git that also shows untrack? i mean status shows them!!! maybe git feature request here this has taken all the fun out of actual task which was hard too, but now the uboot port is installed at least google shows i'm not alone. nobody wants to change their repo locally just to get diff out of it, then immediately undoing all changes. hopefully. none of those changes were required at all. none of those frustrated people wanted to touch repo at all. i'm assuming they were also some contributors to some project and wanted to have submittable patch back in 4.* times we had special port submitting command. it did not require magical filemessing. i used that and it worked. now it's gone?! as for backupping the untracked changes in ports tar cJvf sysutils-atf-sun50i_h616.txz sysutils/atf-sun50i_h616/ was much simpler i mean i might as well just tar all new or modified dirs up and give to someone else who's willing (why) to engage in gitmessing. probably with direct ports commit access to make all those changes, maybe create review diff and then commit & push and this the most actually user friendly vcs existing...?help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6B77F3D4-C55D-4C63-9537-EBC151AFA35F>