From: Nanako Shiraishi <nanako3@lavabit.com>
To: Mike Linck <mgl@absolute-performance.com>
Cc: Jens Lehmann <Jens.Lehmann@web.de>,
Michael Witten <mfwitten@gmail.com>,
git@vger.kernel.org
Subject: Re: Questions about branches in git
Date: Fri, 29 Jan 2010 09:03:45 +0900 [thread overview]
Message-ID: <20100129090345.6117@nanako3.lavabit.com> (raw)
In-Reply-To: <69b754db1001281338l58eb4b84t5a5725de294b6cc5@mail.gmail.com>
Quoting Mike Linck <mgl@absolute-performance.com>
> Could anyone point me to a good book that actually describes the style
> of code management that git was intended to support?
You may want to add the result of googling
"Fun with" site:gitster.livejournal.com
to the list of Git documents you read. "Fork from the oldest branch" is one of the techniques Junio teaches often and many of his other techiniques are built upon.
He not just teaches useful techniques but explains a lot about the reasoning behind them in his Git book. His blog articles have similar explanations on many topics I saw in his book but not in other places. It is a useful substitute until his book gets translated to English for people who don't read Japanese.
--
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
next prev parent reply other threads:[~2010-01-29 0:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 18:44 Questions about branches in git Mike Linck
2010-01-28 20:03 ` Michael Witten
2010-01-28 20:20 ` Michael Witten
2010-01-28 20:35 ` Michael Witten
2010-01-28 21:17 ` Mike Linck
2010-01-28 21:29 ` Jens Lehmann
2010-01-28 21:38 ` Mike Linck
2010-01-28 23:07 ` Heiko Voigt
2010-01-29 0:03 ` Nanako Shiraishi [this message]
2010-01-29 3:03 ` Junio C Hamano
2010-01-28 22:04 ` Nicolas Pitre
2010-01-28 22:13 ` Eugene Sajine
2010-01-28 22:14 ` David Aguilar
2010-01-28 22:18 ` Michael Witten
2010-01-28 22:56 ` Mike Linck
2010-01-28 23:01 ` Michael Witten
2010-01-29 10:07 ` Peter Krefting
2010-01-28 23:00 ` Martin Langhoff
2010-01-28 23:33 ` Junio C Hamano
2010-01-29 1:16 ` Mike Linck
2010-01-29 10:06 ` Peter Krefting
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=20100129090345.6117@nanako3.lavabit.com \
--to=nanako3@lavabit.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=mfwitten@gmail.com \
--cc=mgl@absolute-performance.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.
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.