On 26/03/2025, 12:45, Oswald Buddenhagen via isync-devel wrote:
> i suppose i could have it print "dry run; no modifications will be
> made." at the start.
That'd be clearer, yes.
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://li
On Wed, Mar 26, 2025 at 12:35:34PM +0100, inwit wrote:
On 26/03/2025, 12:30, Oswald Buddenhagen via isync-devel wrote:
yes, due to the re-consolidation of the output format, there is now no
distinction between "would" and "did" in the output, as it's just
numbers.
Understood. They're just num
On 26/03/2025, 12:30, Oswald Buddenhagen via isync-devel wrote:
> yes, due to the re-consolidation of the output format, there is now no
> distinction between "would" and "did" in the output, as it's just
> numbers.
Understood. They're just numbers but there's no distinction between
"would" and
On Wed, Mar 26, 2025 at 12:23:55PM +0100, inwit wrote:
On 26/03/2025, 11:49, Oswald Buddenhagen via isync-devel wrote:
such a bug was fixed in 1.5.1.
Is it possible that in this last version it doesn't explicitly say what "would
have" done in the final summary?
assuming i understand your que
On 26/03/2025, 11:49, Oswald Buddenhagen via isync-devel wrote:
> On Wed, Mar 26, 2025 at 11:08:26AM +0100, inwit wrote:
>>I'm observing a disturbing behaviour of mbsync, both in v1.5.0 and in
>>v1.5.1. When I add the --dry-run flag, mbsync ignores it and does alter
>>my mailboxes, both far and nea
On Wed, Mar 26, 2025 at 11:08:26AM +0100, inwit wrote:
I'm observing a disturbing behaviour of mbsync, both in v1.5.0 and in
v1.5.1. When I add the --dry-run flag, mbsync ignores it and does alter
my mailboxes, both far and near.
such a bug was fixed in 1.5.1.
did you confirm with `mbsync -v` t
Update: it appears that the command line --pull flag is also ignored. :(
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
Hi,
I'm observing a disturbing behaviour of mbsync, both in v1.5.0 and in v1.5.1.
When I add the --dry-run flag, mbsync ignores it and does alter my mailboxes,
both far and near. I've asked a colleague to try and they've confirmed this. I
think this might be an important bug, with potentially h