Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH] vcs_info: add 'find-deepest' zstyle
- X-seq: zsh-workers 47490
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Frank Terbeck <ft@xxxxxxx>
- Subject: Re: [PATCH] vcs_info: add 'find-deepest' zstyle
- Date: Fri, 23 Oct 2020 17:56:22 -0700
- Archived-at: <https://zsh.org/workers/47490>
- Archived-at: <http://www.zsh.org/sympa/arcsearch_id/zsh-workers/2020-10/CAH%2Bw%3D7ZcVgo8JK_2%3Dzw1qNjOBm71QNGr9ppEARsnM_afp2phvQ%40mail.gmail.com>
- Authentication-results: zsh.org; iprev=pass (mail-ot1-f66.google.com) smtp.remote-ip=209.85.210.66; dkim=pass header.d=brasslantern-com.20150623.gappssmtp.com header.s=20150623 header.a=rsa-sha256; dmarc=none header.from=brasslantern.com; arc=none
- Cc: "zsh-workers@xxxxxxx" <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VknxaFQegsXzmdY58lZwnRgObCQLHRyJI5Alt9UqhrY=; b=R5A10UKiq7dy8qSvvjoQTTuPZgnxjRxEy7ZTy6IzZQ2lQj/APk+aoo2iVRetM8pFTO rmy56hG9o4/gP8TggL6qhX2Sh3BRBETsMM6HJUVjMdFi3NfRIf0wX7vYchoHg2Pg3rBo 1fZ3s94Ocw3s5KzJhTVC0qMbP59ZgOdzrdtyzCcbMFWsLNsGt+b/T8XN9GMYe+atl513 GLvCOo0Uzd49ijtPRI97GnWIBSMqrqQ9+XdrQ/QvE1l2nNYkKWUEUDKUhmo+oYfoAJyR u2rOnXHHDTwGHd84O3vuUdANRVJMkY/mXIpB4TaIZ/Az5yfwdcW6KoevBwAlZWzZ4Pvo 3ATQ==
- In-reply-to: <87mu0clbw2.fsf@ft.bewatermyfriend.org>
- List-archive: <http://www.zsh.org/sympa/arc/zsh-workers>
- List-help: <mailto:sympa@zsh.org?subject=help>
- List-id: <zsh-workers.zsh.org>
- List-owner: <mailto:zsh-workers-request@zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- List-subscribe: <mailto:sympa@zsh.org?subject=subscribe%20zsh-workers>
- List-unsubscribe: <mailto:sympa@zsh.org?subject=unsubscribe%20zsh-workers>
- References: <20201023083444.1565608-1-mezin.alexander@gmail.com> <20201023234855.5a0c6290@tarpaulin.shahaf.local2> <87mu0clbw2.fsf@ft.bewatermyfriend.org>
- Sender: zsh-workers-request@xxxxxxx
On Fri, Oct 23, 2020 at 5:13 PM Frank Terbeck <ft@xxxxxxx> wrote:
>
> I, for one, vastly prefer the current behaviour. I don't think nesting
> repositories is all that common. Even when I was using many different
> systems, never did I have a need for that.
At my $WORK we have two related but distinct code bases, an older
version of the platform that is maintained for several longtime
customers and the modern version used by all new customers. The old
code base is in CVS, the new code base (which incorporates a large
subset of the old) has been moved to git. Occasionally there are
bugfixes that need to be ported from one to the other within that
shared subset. Maintaining nested repositories has been useful for
this situation, but it's difficult to get vcs_info to select the
correct one.
That said, I'm not sure "deepest" reflects the right behavior either.
I'd pretty much need to select the repository that differs from the
current working file, whichever one that is at the time.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author