Am 11.03.2016 um 03:57 schrieb Mikael Magnusson:
You can have /usr/src/git/master, /usr/src/git/some-work-tree, etc,
and /usr/src/git itself is not a git repository at all. That way
/usr/src only has one git-related directory and no worktrees are
nested.
I started using separate worktrees recen
On Tue, Mar 15, 2016 at 8:56 PM, Johannes Schindelin
wrote:
> Sure. And with the repository being put elsewhere, you also buy the tedium
> to no longer be able to simply "less .git/rebase-apply/patch". Which I
> have to type *a lot*. You win some, you lose some. If you ask me, you lose
> some more
Hi Duy,
On Tue, 15 Mar 2016, Duy Nguyen wrote:
> On Tue, Mar 15, 2016 at 1:53 PM, Johannes Schindelin
> wrote:
> >> That approach to implement the UI that directly faces the end users
> >> via scripting would let your users choose layouts more flexibly.
> >> Some people may want a repository and
On Tue, Mar 15, 2016 at 1:53 PM, Johannes Schindelin
wrote:
>> That approach to implement the UI that directly faces the end users
>> via scripting would let your users choose layouts more flexibly.
>> Some people may want a repository and its worktrees next to each
>> other, some others may want
Hi Junio,
On Thu, 10 Mar 2016, Junio C Hamano wrote:
> Duy Nguyen writes:
>
> >> Granted, "git worktree remove" should be the work horse. But why not have
> >> two ways to skin the same cat? I, again, would prefer the short 'n sweet
> >> "git branch -d -w pull-rebase-prefix" invocation.
> >
> >
Hi Mikael,
On Fri, 11 Mar 2016, Mikael Magnusson wrote:
> On Thu, Mar 10, 2016 at 2:21 PM, Johannes Schindelin
> wrote:
> > Hi Duy,
> >
> > On Thu, 10 Mar 2016, Duy Nguyen wrote:
> >
> >> On Thu, Mar 10, 2016 at 6:34 PM, Johannes Schindelin
> >> wrote:
> >> > One possible improvement would be t
Duy Nguyen writes:
>> Granted, "git worktree remove" should be the work horse. But why not have
>> two ways to skin the same cat? I, again, would prefer the short 'n sweet
>> "git branch -d -w pull-rebase-prefix" invocation.
>
> If you put effort into making it happen, I'm not stopping you :)
I
On Thu, Mar 10, 2016 at 2:21 PM, Johannes Schindelin
wrote:
> Hi Duy,
>
> On Thu, 10 Mar 2016, Duy Nguyen wrote:
>
>> On Thu, Mar 10, 2016 at 6:34 PM, Johannes Schindelin
>> wrote:
>> > One possible improvement would be to add "/xyz/" to the parent
>> > repository's .git/info/exclude, but this de
On Thu, Mar 10, 2016 at 8:21 PM, Johannes Schindelin
wrote:
> Hi Duy,
>
> On Thu, 10 Mar 2016, Duy Nguyen wrote:
>
>> On Thu, Mar 10, 2016 at 6:34 PM, Johannes Schindelin
>> wrote:
>> > The invention of the `git worktree` command changed this developer's
>> > working style dramatically. Rather th
On Thu, Mar 10, 2016 at 6:51 AM, Duy Nguyen wrote:
> On Thu, Mar 10, 2016 at 6:34 PM, Johannes Schindelin
> wrote:
>> The invention of the `git worktree` command changed this developer's
>> working style dramatically. Rather than switching between branches all
>> the time, topic branches are crea
Hi Duy,
On Thu, 10 Mar 2016, Duy Nguyen wrote:
> On Thu, Mar 10, 2016 at 6:51 PM, Duy Nguyen wrote:
> >> It gets rather tiresome, and also typo-prone, to call "git branch xyz
> >> upstream/master && git worktree add xyz xyz" all the time.
> >
> > You can actually do "git worktree -b xyz xyz upst
Hi Duy,
On Thu, 10 Mar 2016, Duy Nguyen wrote:
> On Thu, Mar 10, 2016 at 6:34 PM, Johannes Schindelin
> wrote:
> > The invention of the `git worktree` command changed this developer's
> > working style dramatically. Rather than switching between branches all
> > the time, topic branches are crea
On Thu, Mar 10, 2016 at 6:51 PM, Duy Nguyen wrote:
>> It gets rather tiresome, and also typo-prone, to call "git branch xyz
>> upstream/master && git worktree add xyz xyz" all the time.
>
> You can actually do "git worktree -b xyz xyz upstream/master" for the
> same effect. Maybe we can avoid "xyz
On Thu, Mar 10, 2016 at 6:34 PM, Johannes Schindelin
wrote:
> The invention of the `git worktree` command changed this developer's
> working style dramatically. Rather than switching between branches all
> the time, topic branches are created and checked out in newly-added
> worktrees, to be rewor
The invention of the `git worktree` command changed this developer's
working style dramatically. Rather than switching between branches all
the time, topic branches are created and checked out in newly-added
worktrees, to be reworked and refined until the topic branch is either
merged into `master`
15 matches
Mail list logo
