From: linux@horizon.com
To: junkio@cox.net, kent@lysator.liu.se
Cc: git@vger.kernel.org, linux@horizon.com
Subject: Re: [DRAFT 2] Branching and merging with git
Date: 22 Nov 2006 10:17:22 -0500 [thread overview]
Message-ID: <20061122151722.13879.qmail@science.horizon.com> (raw)
In-Reply-To: <m3d57g629q.fsf@ceres.unit.liu.se>
Thank you both for the fixes. The features that I didn't know about!
On a higher-level note, is it getting too long?
The explanations of inter-repository sharing and branch
manipulation complement each other nicely, but I'm worried the
combination is a bit intimidating in size.
Still, people will want to know most of it eventually, so maybe it's
next parent reply other threads:[~2006-11-22 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3d57g629q.fsf@ceres.unit.liu.se>
2006-11-22 15:17 ` linux [this message]
2006-11-18 1:11 [DRAFT] Branching and merging with git Junio C Hamano
2006-11-20 23:51 ` [DRAFT 2] " linux
2006-12-04 1:19 ` J. Bruce Fields
2006-12-04 7:23 ` J. Bruce Fields
2006-12-04 10:56 ` Johannes Schindelin
2006-12-15 21:38 ` Jakub Narebski
2006-12-15 21:41 ` J. Bruce Fields
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=20061122151722.13879.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=kent@lysator.liu.se \
/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).