From: Petr Baudis <pasky@ucw.cz>
To: Scott Chacon <schacon@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-scm.com transition
Date: Tue, 16 Dec 2008 12:41:39 +0100 [thread overview]
Message-ID: <20081216114138.GM12856@machine.or.cz> (raw)
In-Reply-To: <d411cc4a0812151007n1be9ce95h92c8c11592ea5f9d@mail.gmail.com>
Hi,
On Mon, Dec 15, 2008 at 10:07:05AM -0800, Scott Chacon wrote:
> I've been working on some docs, like an easy reference, that I could
> put up at git-scm.com. I was wondering if we were still planning on
> transitioning the site from git.or.cz -> git-scm.com?
sure - I just need to be prodded about it, as I said. ;-)
> Is there anything I need to do to help you with that? Are there any
> elements missing still?
hmm... I'm really busy before the end of the year, but this should
take just a really short while by now, so let's see if there are still
some nits:
"$ git clone git://github.com/git/hello-world.git" on the
frontpage overflows from the box for me, and so does "git commit -m
'Initial commit'" in the other box. I work on smallish notebook with
1024x768 resolution, but there are still wide white stripes on the
sides.
Mention FAQ in the "Got a question?" box?
Migrate the SVN crash course to git-scm.com too? Would make
sense, imho. Or maybe we can just throw it on the wiki.
Has anyone reviewed " Pragmatic Version Control Using Git by
Travis Swicegood " if we advertise it on the homepage? I remember
looking at some very early preview and feeling quite uncomfortable
about it. Mentioning a book on the homepage is some kind of an
endorsement.
Merge "Multimedia" into "Videos"?
I'm wondering if the "Related Tools" section shouldn't get a
kind of facelift (as e.g. by now imho people are perceiving gitk,
git-gui and gitweb all as integral git components, you might want to
mention TopGit instead of Cogito, etc.) and the 4x4 format is probably
not too appropriate (the hosting sites aren't a natural fit there, and I
chose it originally only to reduce the vertical length of the
single-page homepage). But that's certainly not a blocking issue for the
redirect.
--
Petr "Pasky" Baudis
The average, healthy, well-adjusted adult gets up at seven-thirty
in the morning feeling just terrible. -- Jean Kerr
next parent reply other threads:[~2008-12-16 11:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d411cc4a0812151007n1be9ce95h92c8c11592ea5f9d@mail.gmail.com>
2008-12-16 11:41 ` Petr Baudis [this message]
[not found] ` <d411cc4a0901011040h4ab97aag20de54a6e138a4ec@mail.gmail.com>
2009-01-05 16:40 ` [ANNOUNCE] Git homepage change Petr Baudis
2009-01-05 18:57 ` Miklos Vajna
2009-01-05 19:03 ` Miklos Vajna
2009-01-05 22:52 ` [PATCH] get_authors.sh, author.rb: use -s option of git shortlog Adeodato Simó
2009-01-05 23:54 ` Miklos Vajna
2009-01-05 19:40 ` [ANNOUNCE] Git homepage change Mike Hommey
2009-01-05 21:27 ` David Bryson
2009-01-06 1:49 ` Scott Chacon
2009-01-06 2:17 ` Baz
2009-01-06 2:25 ` Baz
2009-01-06 2:43 ` Miklos Vajna
2009-01-06 4:24 ` Boyd Lynn Gerber
2009-01-06 8:54 ` Miklos Vajna
2009-01-06 16:12 ` Boyd Lynn Gerber
2009-01-06 20:40 ` Miklos Vajna
2009-01-06 9:07 ` Adeodato Simó
2009-01-05 20:16 ` Felipe Oliveira Carvalho
2009-01-05 20:33 ` Scott Chacon
2009-01-05 20:51 ` Boyd Lynn Gerber
2009-01-05 20:27 ` Ted Pavlic
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=20081216114138.GM12856@machine.or.cz \
--to=pasky@ucw.cz \
--cc=git@vger.kernel.org \
--cc=schacon@gmail.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 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).