From: "J. Bruce Fields" <bfields@fieldses.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Han-Wen Nienhuys <hanwen@xs4all.nl>,
gpermus@gmail.com, hanwen@lilypond.org, git@vger.kernel.org
Subject: Re: [PATCH] cvs-migration document: make the need for "push" more obvious
Date: Wed, 6 Dec 2006 12:24:50 -0500 [thread overview]
Message-ID: <20061206172450.GE1714@fieldses.org> (raw)
In-Reply-To: <20061206171950.GD1714@fieldses.org>
On Wed, Dec 06, 2006 at 12:19:50PM -0500, J. Bruce Fields wrote:
> On Wed, Dec 06, 2006 at 04:16:57PM +0100, Johannes Schindelin wrote:
> Definitely, I agree. So that argues for locating the most import stuff
> as close to start of the document as possible. But obviously there's
> lot of important stuff and you can't do that with everything, so you
> also have to rely on keeping things organized so people can more easily
> skip to the middle.
Hm, but, come to think of it, I agree with you that the "how to commit
and push" really should come earlier, since that's the stuff most people
need to know; currently the order is roughly:
importing a cvs archive
creating a shared repository
committing to a shared repository
We should start out with the assumption that a shared repo is already
set up and make it:
committing to a shared repository
creating a shared repository
importing a cvs archive
which puts it in stuff-most-people-need-to-know to
stuff-less-people-need-to-know order. Maybe the current introduction
should even be postponed to later.
And some day we should move that whole final CVS annotate section
elsewhere.
next prev parent reply other threads:[~2006-12-06 17:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4574AC9E.3040506@gmail.com>
[not found] ` <4574BF70.8070100@lilypond.org>
2006-12-06 0:41 ` git newbie problems Graham Percival
2006-12-06 1:23 ` Jakub Narebski
2006-12-06 9:39 ` Han-Wen Nienhuys
2006-12-06 10:17 ` Jakub Narebski
2006-12-06 10:21 ` Han-Wen Nienhuys
2006-12-06 10:42 ` Johannes Schindelin
2006-12-06 1:35 ` Junio C Hamano
2006-12-06 22:19 ` Daniel Barkalow
2006-12-06 1:52 ` Tom Prince
[not found] ` <el5608$952$2@sea.gmane.org>
2006-12-06 8:01 ` Graham Percival
[not found] ` <45760545.2010801@gmail.com>
[not found] ` <Pine.LNX.4.63.0612060053400.28348@wbgn013.biozentrum.uni-wuerzburg.de>
[not found] ` <45761451.8020006@gmail.com>
[not found] ` <Pine.LNX.4.63.0612060157020.28348@wbgn013.biozentrum.uni-wuerzburg.de>
2006-12-06 9:55 ` git patch Han-Wen Nienhuys
2006-12-06 10:00 ` Junio C Hamano
2006-12-06 10:22 ` Jakub Narebski
[not found] ` <Pine.LNX.4.63.0612061105220.28348@wbgn013.biozentrum.uni-wuerzburg.de>
[not found] ` <457698E0.80207@lilypond.org>
[not found] ` <Pine.LNX.4.63.0612061147540.28348@wbgn013.biozentrum.uni-wuerzburg.de>
2006-12-06 11:27 ` Han-Wen Nienhuys
[not found] ` <20061206.105251.144349770.wl@gnu.org>
2006-12-06 12:27 ` [PATCH] cvs-migration document: make the need for "push" more obvious Johannes Schindelin
2006-12-06 12:32 ` Jakub Narebski
2006-12-06 13:14 ` Johannes Schindelin
2006-12-06 13:27 ` Jakub Narebski
2006-12-06 13:32 ` New users, was " Johannes Schindelin
2006-12-06 14:52 ` J. Bruce Fields
2006-12-06 14:52 ` Han-Wen Nienhuys
2006-12-06 14:58 ` J. Bruce Fields
2006-12-06 15:05 ` Han-Wen Nienhuys
2006-12-06 15:16 ` Johannes Schindelin
2006-12-06 17:19 ` J. Bruce Fields
2006-12-06 17:24 ` J. Bruce Fields [this message]
2006-12-06 17:44 ` Junio C Hamano
2006-12-07 4:18 ` [PATCH] Documentation: reorganize cvs-migration.txt J. Bruce Fields
2006-12-07 5:51 ` Junio C Hamano
2006-12-07 15:21 ` J. Bruce Fields
2006-12-07 14:28 ` Johannes Schindelin
2006-12-07 17:43 ` J. Bruce Fields
2006-12-07 17:50 ` Johannes Schindelin
2006-12-08 3:34 ` J. Bruce Fields
2006-12-08 7:25 ` Junio C Hamano
2006-12-09 3:58 ` J. Bruce Fields
2006-12-06 21:02 ` [PATCH] cvs-migration document: make the need for "push" more obvious Graham Percival
2006-12-06 21:45 ` 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=20061206172450.GE1714@fieldses.org \
--to=bfields@fieldses.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gpermus@gmail.com \
--cc=hanwen@lilypond.org \
--cc=hanwen@xs4all.nl \
/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).