git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Mar 2014, #08; Mon, 31)

From
Duy Nguyen <pclouds@gmail.com>
Date
Apr 1, 2014, 23:40 UTC
Message-ID
<CACsJy8BVXk248VDBi-pAMDY4QpDSbFuAf5qxRxCCq71yGNzpqA@mail.gmail.com>
In-Reply-To
<xmqq38hw272q.fsf@gitster.dls.corp.google.com>
On Wed, Apr 2, 2014 at 2:17 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 10 quoted lines
>> 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).

The --daemon part is probably not worth mentioning because I always have one emacs window open. The problem is switch-buffer based on file name can be confusing ("git.c" and "git.c<2>", which belongs to which checkout?). I ended up modifying files in the wrong checkout all the time.

-- 
Duy
Previous: Junio C HamanoNext: Stephen Leake
Message 4 of 10 in “What's cooking in git.git (Mar 2014, #08; Mon, 31)”
  1. Junio C HamanoApr 1, 2014
  2. Duy NguyenApr 1, 2014
  3. Junio C HamanoApr 1, 2014
  4. Duy NguyenApr 1, 2014
  5. Stephen LeakeApr 2, 2014
  6. Junio C HamanoApr 1, 2014
  7. David KastrupApr 2, 2014
  8. Junio C HamanoApr 2, 2014
  9. Heiko VoigtApr 2, 2014
  10. Junio C HamanoApr 3, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.