From: Jon Loeliger <jdl@freescale.com>
To: Junio C Hamano <junkio@cox.net>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Some ASCII Art
Date: Fri, 07 Oct 2005 14:35:50 -0500 [thread overview]
Message-ID: <1128713749.29904.84.camel@cashmere.sps.mot.com> (raw)
In-Reply-To: <7v8xx67559.fsf@assigned-by-dhcp.cox.net>
On Thu, 2005-10-06 at 15:38, Junio C Hamano wrote:
> Jon Loeliger <jdl@freescale.com> writes:
>
> > Fundamental Git Index Operations
> > Git Index Operations
>
> These two look almost the same.
Yeah, the first one was intended to capture the
operations discussed the first four points of the
"The Workflow" section of the main Git doc page.
The second is "more of same", but the one picture with
every ASCII arc on it was getting confusing and crowded.
> I find the label "commit-tree" on index -> odb in the second
> picture a bit misleading. "commit-tree" takes a tree and zero
> or more commit objects to create a new commit object, so it
> works solely inside odb.
Ah! Of course. Thanks!
> It is good that you mention that "read-tree -u" form updates
> working tree in the second picture.
Discovering how this related was a key insight for me. :-)
> In the same spirit, you
> might also want to mention that "checkout-index -u" updates the
> index (i.e. matches the stat information) in the same picture.
Ooh. Yes! Good idea.
> > Commit DAG Revision Naming
> > ==========================
> >
> > Both node B and C are a commit parents of node A.
>
> I assume that parents are left to right in this picture, that
> is, B's first parent is D, second E, and third F.
Yeah, I even meant to add that sentence before
sending the mail.
> > Is there a way to name node C, E, F, H, I or J?
>
> C = A^2
> E = B^2 = A^^2
> F = B^3 = A^^3
> H = D^2 = B^^2 = A^^^2 = A~2^2
> I = F^ = B^3^ = A^^3^
> J = F^2 = B^3^2 = A^^3^2
Ah!
> They look like line noise ;-)
Indeed. :-)
Would it be a useful option to git-show-branch
that would state the commit SHA1s as well?
% git show-branch --show-revs
* [master] Merge paul's branch
! [origin] Fix drm 'debug' sysfs permissions
! [paul] powerpc: Fix idle.c compile warning
---
+ [06a41091c93e529e6cef68ba60deeb1b9ceabc7f] Merge paul's branch
+ + [05f62a5c049845eab8dfb3aeda55c18a2d4396e3] powerpc: Fix idle.c compile warning
+ + [c16ff7e44883afc05cbf6fde0e6913bb10c66885] powerpc: Define a _sdata symbol
+ + [8dad3f9257414f151cd821bfe01f54d7f52d2507] powerpc: Merge traps.c a bit more
+ + [b3491269f5604e4265ee2f27b47a76ce1e3678b6] powerpc: Use the merged of_device.c with ARCH=powerpc
Thanks for your feedback!
jdl
next prev parent reply other threads:[~2005-10-07 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 18:05 Some ASCII Art Jon Loeliger
2005-10-06 20:38 ` Junio C Hamano
2005-10-07 19:35 ` Jon Loeliger [this message]
2005-10-07 19:42 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1128713749.29904.84.camel@cashmere.sps.mot.com \
--to=jdl@freescale.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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