Re: [Query] Separate hooks for Git worktrees

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [Query] Separate hooks for Git worktrees
From: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
Date: Mon, 13 Nov 2017 08:46:43 +0530
Cc: Junio C Hamano <gitster@xxxxxxxxx>, Git Mailing List <git@xxxxxxxxxxxxxxx>, Vincent Guittot <vincent.guittot@xxxxxxxxxx>
In-reply-to: <CAGZ79kZ8PKBwe+aWTUOgPwV2tNQS7+dUrLTVsWhzemj-e35kaA@mail.gmail.com>
References: <CAKohponsPQC6qTw99+xh1RSu0bZNDSo5TbbZZcYmup3NOW6QmA@mail.gmail.com> <CAGZ79ka9VnzYTYgtWgGAhvgn2LRpP_BCQyVvQ8iC1w9XJnRxEw@mail.gmail.com> <xmqq60aihgod.fsf@gitster.mtv.corp.google.com> <CAGZ79kZ8PKBwe+aWTUOgPwV2tNQS7+dUrLTVsWhzemj-e35kaA@mail.gmail.com>
User-agent: Mutt/1.5.24 (2015-08-30)

On 10-11-17, 10:00, Stefan Beller wrote:
> Well it is the same project with different upstream workflows.
> For example I would imagine that Viresh wants to cherry-pick
> from one branch to another, or even send the same patch
> (just with different commit messages, with or without the
> ChangeId) to the different upstreams?

Right.

-- 
viresh

References:
- [Query] Separate hooks for Git worktrees
  - From: Viresh Kumar
- Re: [Query] Separate hooks for Git worktrees
  - From: Stefan Beller
- Re: [Query] Separate hooks for Git worktrees
  - From: Junio C Hamano
- Re: [Query] Separate hooks for Git worktrees
  - From: Stefan Beller

Prev by Date: Re: [RFC PATCH v3 2/4] branch: re-order function arguments to group related arguments
Next by Date: Re: [add-default-config 2/5] adding default to color
Previous by thread: Re: [Query] Separate hooks for Git worktrees
Next by thread: [PATCH] Documentation: fix typos for the reference in new-command.txt
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]