So I updated this patch to skip the message when checkout is done in a shared repo. However, there is an interesting case below.
[tmp]% bzr init-repo foo
Shared repository with trees (format: 2a)
Location:
shared repository: foo
[tmp]% cd foo
[foo]% /home/parthm/src/bzr.dev/538868-message-for-heavy-checkout/bzr checkout ~/src/bzr.dev/trunk foo
[foo]%
In this case, the entire history is copied so it does take time. I am wondering if we should just stick to the simpler earlier patch. Alternatively, if there is a way to know how many changes need to be pulled we could show the message based on this.
This is still checkout specific and doesn't touch other operations.
So I updated this patch to skip the message when checkout is done in a shared repo. However, there is an interesting case below.
[tmp]% bzr init-repo foo src/bzr. dev/538868- message- for-heavy- checkout/ bzr checkout ~/src/bzr.dev/trunk foo
Shared repository with trees (format: 2a)
Location:
shared repository: foo
[tmp]% cd foo
[foo]% /home/parthm/
[foo]%
In this case, the entire history is copied so it does take time. I am wondering if we should just stick to the simpler earlier patch. Alternatively, if there is a way to know how many changes need to be pulled we could show the message based on this.
This is still checkout specific and doesn't touch other operations.