Re: batch checking for modifications?

2022-11-15 Thread TortoiseSVN on behalf of lorenznl
TortoiseSVN on behalf of H. Niemann wrote: >I would like to check in a batch file, whether my working copy is still >identical to HEAD. > >Reason: an automatic build creates a tag (after the build) and I want to make >sure that the input files are unchanged. why not tag first, then build from

Re: batch checking for modifications?

2022-11-15 Thread TortoiseSVN
How about locking the repository during the bild process? --- Stefan P. Daniel Sahlberg via TortoiseSVN schrieb am Di., 15. Nov. 2022, 09:22: > tisdag 15 november 2022 kl. 08:58:55 UTC+1 skrev H. Niemann: > >> Hello *! >> >> >> >> I would like to check in a batch file, whether my working copy

Re: batch checking for modifications?

2022-11-15 Thread Daniel Sahlberg via TortoiseSVN
tisdag 15 november 2022 kl. 08:58:55 UTC+1 skrev H. Niemann: > Hello *! > > > > I would like to check in a batch file, whether my working copy is still > identical to HEAD. > > > > Reason: an automatic build creates a tag (after the build) and I want to > make sure that the input files are

batch checking for modifications?

2022-11-14 Thread TortoiseSVN on behalf of H. Niemann
Hello *! I would like to check in a batch file, whether my working copy is still identical to HEAD. Reason: an automatic build creates a tag (after the build) and I want to make sure that the input files are unchanged. Steps: 1. Create a fresh working copy 2. Build 3. Commit build