From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: gitk "parent information" in commit window
Date: Sun, 07 Aug 2005 14:17:21 -0700 [thread overview]
Message-ID: <7v4qa1v44e.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0508071351150.3258@g5.osdl.org> (Linus Torvalds's message of "Sun, 7 Aug 2005 13:58:56 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> [ Btw, the patch was generated against a tree that had Paul's hovering
> patches merged. Junio, I don't think you've merged that yet, so this may
> apply better to Paul's tree than to standard git. But I _think_ it will
> apply cleanly to either one ]
Thanks. Since Paul seems to be quite responsive, I'd prefer to
keep pulling from his tree. I just pulled the hovering patches
from his tree and was about to push things out.
next prev parent reply other threads:[~2005-08-07 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 20:58 gitk "parent information" in commit window Linus Torvalds
2005-08-07 21:17 ` Junio C Hamano [this message]
2005-08-07 22:52 ` Paul Mackerras
2005-08-08 0:03 ` A Large Angry SCM
2005-08-08 0:29 ` Junio C Hamano
2005-08-08 3:19 ` A Large Angry SCM
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=7v4qa1v44e.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/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 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 NNTP newsgroup(s).