On wo, 2016-01-27 at 14:12 -0800, Junio C Hamano wrote:
> More seriously, are we confident that the overall worktree support
> is mature enough by now that once we add an experimental feature X
> at version 1, we can promise to keep maintaining it forever at
> version N for any positive integer N?
Duy Nguyen writes:
> On Mon, Feb 1, 2016 at 9:41 AM, Stefan Monnier
> wrote:
>>> One lessor key phrase above is "so far", I think, and another one
>>> you forgot to use is s/which requires/that we know &/, which to me
>>> is a more serious one. IOW, I do think it is premature for us to
>>> say
On Mon, Feb 1, 2016 at 9:41 AM, Stefan Monnier wrote:
>> One lessor key phrase above is "so far", I think, and another one
>> you forgot to use is s/which requires/that we know &/, which to me
>> is a more serious one. IOW, I do think it is premature for us to
>> say that that config split issue
> As a heavy user of the git-new-worktree "hack / script", is there
git-new-workdir
Sorry,
Stefan
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
Mor
> One lessor key phrase above is "so far", I think, and another one
> you forgot to use is s/which requires/that we know &/, which to me
> is a more serious one. IOW, I do think it is premature for us to
> say that that config split issue is the only thing, or to say that
> the issue is best solve
Max Kirillov writes:
> The worktree feature has been used by several people
> already (me included), and do far the only issue which
> requires change in repository layout is the config
> separation. Isn't it enough to be confident?
One lessor key phrase above is "so far", I think, and another o
On Wed, Jan 27, 2016 at 02:12:52PM -0800, Junio C Hamano wrote:
> More seriously, are we confident that the overall worktree support
> is mature enough by now that once we add an experimental feature X
> at version 1, we can promise to keep maintaining it forever at
> version N for any positive int
On Tue, Jan 26, 2016 at 06:44:40PM +0700, Nguyễn Thái Ngọc Duy wrote:
> +WORKTREE VERSIONS AND MIGRATION
> +---
> +Multiple worktree is still an experimental feature and evolving. Every
> +time the behavior is changed, the "worktree version" is stepped
> +up. Worktree ve
On Thu, Jan 28, 2016 at 5:12 AM, Junio C Hamano wrote:
>> +WORKTREE VERSIONS AND MIGRATION
>> +---
>> +Multiple worktree is still an experimental feature and evolving. Every
>> +time the behavior is changed, the "worktree version" is stepped
>> +up. Worktree version is
Nguyễn Thái Ngọc Duy writes:
> Multiple worktree setup is still evolving and its behavior may be
> changed in future. But we do not want to break existing worktree
s/be changed/change/
> setups. A new set of extensions, worktree=X, is recognized to tell Git
> what multiple worktree "version" i
10 matches
Mail list logo
