git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Mar 2014, #08; Mon, 31)
Date: Tue, 01 Apr 2014 12:17:01 -0700	[thread overview]
Message-ID: <xmqq38hw272q.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CACsJy8A9b2eccm_BJMjW5RwWLux90xs7HfUQEn0_jrzhHWeajQ@mail.gmail.com> (Duy Nguyen's message of "Tue, 1 Apr 2014 07:53:37 +0700")

Duy Nguyen <pclouds@gmail.com> writes:

> The basic support is there. Some bells and whistles (e.g. listing
> checkouts) are not, but we can add them when we see the needs. Eric
> and Torsten helped review but no, there hasn't much discussion about
> it, which may be because it's already perfect, or people are not
> interested.

;-)

> Unfortunately, this multiple checkout thing conflicts with how I
> use emacs (--daemon) so I'm not one of its heavy users either. I
> only occastionally make new, short-lived checkouts to test things.

FWIW, I do keep a permanent multi-checkout and I sometimes make
edits, but it is mostly for building other branches while I work on
something else.  When I edit working-tree files there, I do let
emacsclient talk to the emacs I have files open in the primary
working tree, though, so I am not sure what your issues are with
emacs (--daemon).

  reply	other threads:[~2014-04-01 19:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01  0:29 What's cooking in git.git (Mar 2014, #08; Mon, 31) Junio C Hamano
2014-04-01  0:53 ` Duy Nguyen
2014-04-01 19:17   ` Junio C Hamano [this message]
2014-04-01 23:40     ` Duy Nguyen
2014-04-02 23:22       ` emacs buffer names Stephen Leake
2014-04-01 22:03 ` What's cooking in git.git (Mar 2014, #08; Mon, 31) Junio C Hamano
2014-04-02  5:05   ` David Kastrup
2014-04-02 19:41     ` Junio C Hamano
2014-04-02 20:04 ` Heiko Voigt
2014-04-03 17:15   ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq38hw272q.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).