git-kv/test/fold.t

Batch operation
  $ mkdir simple
  $ cd simple
  $ git init --bare -q 2> /dev/null
  $ cd ..
  $ git daemon --base-path=. --export-all --enable=receive-pack --reuseaddr --pid-file=pid --detach
  $ mgit git://localhost/simple#main <<EOF
  > fold 
  > set /bar "Git rocks!"
  > set /foo "Hello World!"
  > exists /bar
  > quit
  > quit
  /"bar" does not exists
  $ mgit git://localhost/simple#main <<EOF
  > list /
  > get /bar
  > get /foo
  > quit
  - bar
  - foo
  00000000: 4769 7420 726f 636b 7321                 Git rocks!
  00000000: 4865 6c6c 6f20 576f 726c 6421            Hello World!
  $ cd simple
  $ git log main --pretty=oneline | wc -l
  1
  $ cd ..
  $ kill $(cat pid)
Implement the batch function according to the documentation This implementation is much more close to the documentation & fold all changes into one commit. Then, it pushes this commit remotely. This commit deleted local changes which complexify the codebase for a questionable interest. As the documentation said, any changes are delayed and not directly "committed" until the end of the given function. For instance: > batch > set /bar "Bar" > exists /bar /bar does not exists is an expected behavior. Only after a quit (which delimit the end of the batch process), /bar will be committed and will exist! 2022-10-29 19:18:10 +00:00			`Batch operation`
			`$ mkdir simple`
			`$ cd simple`
			`$ git init --bare -q 2> /dev/null`
			`$ cd ..`
			`$ git daemon --base-path=. --export-all --enable=receive-pack --reuseaddr --pid-file=pid --detach`
			`$ mgit git://localhost/simple#main <<EOF`
Rename batch to change_and_push (and implement batch as noop) 2022-10-31 17:13:15 +00:00			`> fold`
Implement the batch function according to the documentation This implementation is much more close to the documentation & fold all changes into one commit. Then, it pushes this commit remotely. This commit deleted local changes which complexify the codebase for a questionable interest. As the documentation said, any changes are delayed and not directly "committed" until the end of the given function. For instance: > batch > set /bar "Bar" > exists /bar /bar does not exists is an expected behavior. Only after a quit (which delimit the end of the batch process), /bar will be committed and will exist! 2022-10-29 19:18:10 +00:00			`> set /bar "Git rocks!"`
			`> set /foo "Hello World!"`
			`> exists /bar`
			`> quit`
			`> quit`
			`/"bar" does not exists`
			`$ mgit git://localhost/simple#main <<EOF`
			`> list /`
			`> get /bar`
			`> get /foo`
			`> quit`
			`- bar`
			`- foo`
			`00000000: 4769 7420 726f 636b 7321 Git rocks!`
			`00000000: 4865 6c6c 6f20 576f 726c 6421 Hello World!`
			`$ cd simple`
			`$ git log main --pretty=oneline \| wc -l`
			`1`
			`$ cd ..`
			`$ kill $(cat pid)`