From: David Turner <dturner@twopensource.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
Christian Couder <chriscool@tuxfamily.org>,
git <git@vger.kernel.org>,
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Subject: Re: [PATCH/RFC 0/2] bisect per-worktree
Date: Sat, 01 Aug 2015 01:43:17 -0400 [thread overview]
Message-ID: <1438407797.4735.30.camel@twopensource.com> (raw)
In-Reply-To: <CAP8UFD0aCSW3JxneHvSEE3T6zQtgipp5nhWT9VpMqHAmzd_e3Q@mail.gmail.com>
On Sat, 2015-08-01 at 06:04 +0200, Christian Couder wrote:
>
> Le 1 août 2015 09:01, "David Turner" <dturner@twopensource.com> a
> écrit :
> >
> > This is RFC because I'm not sure why show-ref only works on refs/
> (and
> > whether it should learn to look in worktree-refs/). I'm also not
> sure
> > whether there are other changes I should make to refs.c to handle
> > per-worktree refs; I basically did the simplest thing I could think
> of
> > to start with.
>
> (Sorry, I am answering from my phone, as I am having a vacation. )
Enjoy your vacation.
> I wonder what would happen if people upgrade in the middle of a
> bisection or if they have scripts using "bisect/bad" for example.
Junio told me not to worry about this, so I didn't.
next parent reply other threads:[~2015-08-01 5:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP8UFD0aCSW3JxneHvSEE3T6zQtgipp5nhWT9VpMqHAmzd_e3Q@mail.gmail.com>
2015-08-01 5:43 ` David Turner [this message]
2015-07-31 23:56 [PATCH/RFC 0/2] bisect per-worktree David Turner
2015-08-01 3:59 ` Michael Haggerty
2015-08-01 5:12 ` Junio C Hamano
2015-08-01 5:55 ` David Turner
2015-08-01 6:51 ` Michael Haggerty
2015-08-02 18:24 ` Junio C Hamano
2015-08-03 12:35 ` Duy Nguyen
2015-08-03 19:49 ` David Turner
2015-08-03 21:14 ` Junio C Hamano
2015-08-03 23:09 ` Duy Nguyen
2015-08-03 23:20 ` David Turner
2015-08-03 13:02 ` Duy Nguyen
2015-08-03 14:03 ` Duy Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1438407797.4735.30.camel@twopensource.com \
--to=dturner@twopensource.com \
--cc=chriscool@tuxfamily.org \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=pclouds@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.