From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: phillip.wood@dunelm.org.uk
Cc: Emily Shaffer <emilyshaffer@google.com>,
Matthew DeVore <matvore@google.com>,
git@vger.kernel.org, Matthew DeVore <matvore@gmail.com>,
matvore@comcast.net, jonathantanmy@google.com,
jrnieder@gmail.com, steadmon@google.com
Subject: Re: [RFC] xl command for visualizing recent history
Date: Fri, 1 Nov 2019 19:58:01 +0100 (CET) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1911011956580.46@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <b0169b2b-0d8a-ee27-d0f4-6c7a6df55b5d@gmail.com>
Hi Phillip,
On Thu, 31 Oct 2019, Phillip Wood wrote:
> On 31/10/2019 08:26, Johannes Schindelin wrote:
>
> > Finally, I could imagine that in this context, we would love to have
> > refs that are purely intended for interactive use, and therefore it
> > would make sense to try to bind them to the process ID of the
> > process calling `git`, i.e. the interactive shell. That way, when I
> > have two terminal windows, they would "own" their separate ephemeral
> > refs.
>
> I like that idea, though I think it should probably be based around
> getsid() rather than getppid() (I'm not sure how that translates to
> windows)
Good idea.
On Windows, we would probably use the `HANDLE` of the associated Win32
Console.
Ciao,
Dscho
next prev parent reply other threads:[~2019-11-01 18:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 0:30 [RFC] xl command for visualizing recent history Matthew DeVore
2019-10-31 0:39 ` Emily Shaffer
2019-10-31 8:26 ` Johannes Schindelin
2019-10-31 20:04 ` Phillip Wood
2019-11-01 18:58 ` Johannes Schindelin [this message]
2020-01-03 20:14 ` Matthew DeVore
2020-01-03 21:30 ` Junio C Hamano
2020-01-04 20:30 ` Johannes Schindelin
2020-01-04 22:56 ` Junio C Hamano
2020-01-04 21:21 ` Johannes Schindelin
2020-02-07 1:39 ` Matthew DeVore
2020-01-03 2:51 ` Matthew DeVore
2019-10-31 10:16 ` Johannes Schindelin
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=nycvar.QRO.7.76.6.1911011956580.46@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=matvore@comcast.net \
--cc=matvore@gmail.com \
--cc=matvore@google.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=steadmon@google.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).