Re: [commit] master: build: also consider builds off of git with `git clone --depth 1`

On Wed, Dec 04, 2024 at 05:28:33PM +0100, Oswald Buddenhagen via isync-devel wrote: > but maybe this could be still handled better? i guess not, as the branch > name above is meaningless, and presumably no other refs are present? does > gitk --all show anything sensible in this repo? it's a remo

Re: [commit] master: build: also consider builds off of git with `git clone --depth 1`

On Wed, Dec 04, 2024 at 11:15:29AM -0500, Paymon wrote: spoke to early; it's git-branch that returns something like this: * (HEAD detached at refs/git-r3/HEAD) that escapes our regex. i would pass `--always` unconditionally to be defensive about it; what do you think? i did that, with a force

Re: [commit] master: build: also consider builds off of git with `git clone --depth 1`

you beat me to it; please discard the other patch. -- Paymon ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel

build: take count of detached HEAD

-- Paymon >From 372f929bbe0ab29f35d515ad13f21b8d851941ef Mon Sep 17 00:00:00 2001 From: Paymon Date: Wed, 4 Dec 2024 11:18:20 -0500 Subject: [PATCH] build: take count of detached HEAD this should broden the coverage of 8920b6a for all cases. Signed-off-by: Paymon MARANDI ---

[commit] branch 'master' rewound

The branch 'master', previously at 8920b6a, has been rewound by 1 revision(s) to 15c7e02. ___ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel

[commit] master: build: also consider builds off of git with `git clone --depth 1`

commit 884413b48871361cf6c0cfa41d01c22ed1ec8d30 Author: Paymon MARANDI AuthorDate: Tue Dec 3 15:25:09 2024 -0500 Commit: Oswald Buddenhagen CommitDate: Wed Dec 4 17:20:49 2024 +0100 build: also consider builds off of git with `git clone --depth 1` one case where this could h

Re: [commit] master: build: also consider builds off of git with `git clone --depth 1`

On Wed, Dec 04, 2024 at 10:50:43AM -0500, Paymon wrote: > On Wed, Dec 04, 2024 at 08:41:44AM +, ossi via isync-devel wrote: > > commit 8920b6a1db443aac00783f7754a05852bb1bc71c > > Author: Paymon MARANDI > > AuthorDate: Tue Dec 3 15:25:09 2024 -0500 > > Commit: Oswald Buddenhagen > > C

Re: [commit] master: build: also consider builds off of git with `git clone --depth 1`

On Wed, Dec 04, 2024 at 10:50:43AM -0500, Paymon wrote: +++ b/version.sh @@ -22,7 +22,7 @@ else # find out whether we have local work, and if so, collapse it into # a single suffix. otherwise, we'd cause pointless rebuilds during # development. - gver=$(git describe

Re: [commit] master: build: also consider builds off of git with `git clone --depth 1`

On Wed, Dec 04, 2024 at 08:41:44AM +, ossi via isync-devel wrote: > commit 8920b6a1db443aac00783f7754a05852bb1bc71c > Author: Paymon MARANDI > AuthorDate: Tue Dec 3 15:25:09 2024 -0500 > Commit: Oswald Buddenhagen > CommitDate: Wed Dec 4 09:36:28 2024 +0100 > > build: also consid

Re: IMAP Timeouts During Local Operations—Correct Behaviour?

On Tue, Dec 03, 2024 at 04:12:09PM +, Sabahattin Gucukoglu via isync-devel wrote: So my question is this: is it expected behaviour that timeouts occur because of long local operations, yes, sort of. and is it *correct* or desirable behaviour? certainly not desirable. Isn’t the “right

[commit] master: build: also consider builds off of git with `git clone --depth 1`

commit 8920b6a1db443aac00783f7754a05852bb1bc71c Author: Paymon MARANDI AuthorDate: Tue Dec 3 15:25:09 2024 -0500 Commit: Oswald Buddenhagen CommitDate: Wed Dec 4 09:36:28 2024 +0100 build: also consider builds off of git with `git clone --depth 1` one case where this could h