Re: multiple-commit cherry-pick?
Linus Torvalds <torvalds@linux-foundation.org> writes:
Show 6 quoted lines
> So we could make a '{ }' in the argument space basically do a SHA1
> expansion of the range inside, and imply --no-walk. It's _not_ entirely
> trivial, because we'd need to handle the fact that object flags are
> sticky, and clear them in between invocations of multiple ranges, but it's
> not _fundmanetally_ difficult. It's just that somebody would need to do
> it.Wouldn't you lose the nice streaming output (iow short latency)?