The Nest
Explore
437
The sound distributed version control system

#615 Pijul record creates empty change

Closed on January 12, 2022
O01eg on January 10, 2022

When I record changes in pijul 1.0.0-alpha.57 it somehow creates empty change before actual change. 

$ pijul record
Password for "/home/oleg/.config/pijul/secretkey.json": 
Hash: 5U5MRHZ64PDJEKGK37TNWOWQJV34UJP2EQFSTMTU7CM7MEIHRZXQC
$ pijul log

Change 5U5MRHZ64PDJEKGK37TNWOWQJV34UJP2EQFSTMTU7CM7MEIHRZXQC
Author: 6xbZsEkjnZZpiD9GashW1D8feyXEWg43TbWGcJeUX1KQ
Date: 2022-01-10 20:49:47.733672008 UTC

    Update dependencies

Change QUDMKVDAL76ONZMD6XG5OMZHFCHUMWDMHYIBRY22RL7JJ4AEEM4AC
Author: 
Date: 2022-01-10 20:49:51.512154966 UTC

QUDMKVDAL76ONZMD6XG5OMZHFCHUMWDMHYIBRY22RL7JJ4AEEM4AC have later date but 5U5MRHZ64PDJEKGK37TNWOWQJV34UJP2EQFSTMTU7CM7MEIHRZXQC depends on it

tankf33der on January 11, 2022

QUD change is a special root of the tree of changes.

tankf33der closed this discussion on January 11, 2022
O01eg on January 11, 2022

Why did it appear after all previous changes and before real change? Should I be an author of this change?

O01eg reopened this discussion on January 11, 2022
pmeunier on January 12, 2022

It’s a mostly empty change, there for technical reasons explained here, see “One minor incovenience”.

pmeunier closed this discussion on January 12, 2022
O01eg on January 12, 2022

It looks like “Backwards-compatibility” in my case