Date: Thu, 26 Oct 2023 09:48:03 -0400 From: "Dan Langille" <dan@langille.org> To: "Tatsuki Makino" <tatsuki_makino@hotmail.com>, freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: output of RUN_DEPENDS changes unexpectedly Message-ID: <99f6b123-7c6f-4273-9ead-6e9cf5c83e10@app.fastmail.com> In-Reply-To: <SI2PR01MB5036417EF1A48C33B28166AEFADEA@SI2PR01MB5036.apcprd01.prod.exchangelabs.com> References: <51D9023C-5829-4615-9A16-3060853CD9C0@langille.org> <SI2PR01MB5036417EF1A48C33B28166AEFADEA@SI2PR01MB5036.apcprd01.prod.exchangelabs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 24, 2023, at 11:38 PM, Tatsuki Makino wrote: > Hello. > > I don't know what it is, but as a maintainer but not a committer, I > don't use features related to git branch. > Changes are made directly to files that are checkout-ed, and when > updates are made by pull, etc., stash takes care of everything. > > git stash push --all -- :/ > git pull --autostash ... > git stash pop > git status --show-stash > > Submitted patches are required to have been created with git > format-path, which requires a git commit. > So I do the commit locally, but do a soft reset as soon as the patch is > collected. > > git restore --staged :/ > git add category/portname > git commit > git format-patch -1 HEAD > git reset --soft HEAD^ > > Is there some other way to do it better? :) > Wasn't it like this? :) I don't know. I've never done format-patch or reset when submitting a change. However, I commit changes, so it might be different. Your question might get answers in a new thread. -- Dan Langille dan@langille.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?99f6b123-7c6f-4273-9ead-6e9cf5c83e10>