From: Yasushi SHOJI <yashi@atmark-techno.com>
To: "J. Bruce Fields" <bfields@citi.umich.edu>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] glossary: Add definitions for dangling and unreachable objects
Date: Mon, 05 Mar 2007 09:45:48 +0900 [thread overview]
Message-ID: <874pp08qmb.wl@mail2.atmark-techno.com> (raw)
In-Reply-To: <117304556139-git-send-email-bfields@citi.umich.edu>
At Sun, 4 Mar 2007 16:59:16 -0500,
J. Bruce Fields wrote:
>
> From: Yasushi SHOJI <yashi@atmark-techno.com>
>
> Define "dangling" and "unreachable" objects. Modified from original
> text proposed by Yasushi Shoji.
>
> Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
If possible, please include
http://article.gmane.org/gmane.comp.version-control.git/40662
that's the original. otherwise
Acked-by: Yasushi SHOJI <yashi@atmark-techno.com>
thanks,
--
yashi
next prev parent reply other threads:[~2007-03-05 0:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-04 21:59 Documentation (mostly user manual) patches J. Bruce Fields
2007-03-04 21:59 ` [PATCH] Documentation: mention module option to git-cvsimport J. Bruce Fields
2007-03-04 21:59 ` [PATCH] user-manual: reset to ORIG_HEAD not HEAD to undo merge J. Bruce Fields
2007-03-04 21:59 ` [PATCH] user-manual: ensure generated manual references stylesheet J. Bruce Fields
2007-03-04 21:59 ` [PATCH] user-manual: insert earlier of mention content-addressable architecture J. Bruce Fields
2007-03-04 21:59 ` [PATCH] user-manual: how to replace commits older than most recent J. Bruce Fields
2007-03-04 21:59 ` [PATCH] user-manual: more detailed merge discussion J. Bruce Fields
2007-03-04 21:59 ` [PATCH] glossary: Add definitions for dangling and unreachable objects J. Bruce Fields
2007-03-05 0:45 ` Yasushi SHOJI [this message]
2007-03-16 12:44 ` [PATCH] user-manual: ensure generated manual references stylesheet Robert Pluim
2007-03-16 14:24 ` J. Bruce Fields
[not found] ` <7C0AC446-57CA-480B-A14E-1E861E2FCBA7@silverinsanity.com>
2007-03-16 15:36 ` J. Bruce Fields
[not found] ` <7DA766E4-D88F-4248-BD29-1E0B403BF0BE@silverinsanity.com>
2007-03-16 17:02 ` J. Bruce Fields
2007-03-05 3:14 ` Documentation (mostly user manual) patches Junio C Hamano
2007-03-05 18:38 ` J. Bruce Fields
2007-03-11 4:35 ` J. Bruce Fields
2007-03-11 4:35 ` [PATCH 1/6] glossary: fix overoptimistic automatic linking of defined terms J. Bruce Fields
2007-03-11 4:35 ` [PATCH 2/6] user-manual: fix inconsistent example J. Bruce Fields
2007-03-11 4:35 ` [PATCH 3/6] user-manual: fix inconsistent use of pull and merge J. Bruce Fields
2007-03-11 4:35 ` [PATCH 4/6] user-manual: fix missing colon in git-show example J. Bruce Fields
2007-03-11 4:35 ` [PATCH 5/6] user-manual: fix rendering of history diagrams J. Bruce Fields
2007-03-11 4:35 ` [PATCH 6/6] user-manual: install user manual stylesheet with other web documents J. Bruce Fields
2007-03-11 4:39 ` [PATCH 2/6] user-manual: fix inconsistent example J. Bruce Fields
2007-03-13 19:31 ` Ramsay Jones
2007-03-14 23:19 ` J. Bruce Fields
2007-03-11 5:35 ` Documentation (mostly user manual) patches Junio C Hamano
2007-03-07 20:19 ` Ramsay Jones
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=874pp08qmb.wl@mail2.atmark-techno.com \
--to=yashi@atmark-techno.com \
--cc=bfields@citi.umich.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.