git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Adam" <thomas.adam22@gmail.com>
To: "Scott Chacon" <schacon@gmail.com>
Cc: "git list" <git@vger.kernel.org>
Subject: Re: Git Books
Date: Sat, 6 Dec 2008 12:09:59 +0000	[thread overview]
Message-ID: <18071eea0812060409y33680534p6b9ad56dd5043538@mail.gmail.com> (raw)
In-Reply-To: <d411cc4a0812060358ub640ea3kd04072c5640eef68@mail.gmail.com>

2008/12/6 Scott Chacon <schacon@gmail.com>:
> So, since I'm near the beginning of this process, I was wondering if
> the group had any feedback as to what might be super helpful to
> include.  I mean, I have a pretty good layout and all, but if you
> wanted to point me to some threads that tend to crop up in the mailing
> list and IRC channel from relative newcomers that I might be able to
> nip in the bud, I would like to.  I'm addressing the stuff that _I_
> hear a lot, and I'm scanning the IRC logs and list for topics, but I
> figured many of you must answer the same questions all the time, too.

Perhaps you're able to share this layout?  Whilst I am not about to go
trawling through the archives, one thing I do know that comes up a
lot, isn't so much how to use git to mimick coming from another SCM,
but more workflows -- that's the big stumbling point for people using
Git.  I know I'd like to see that aspect in a Git book heavily
addressed.

-- Thomas Adam

  reply	other threads:[~2008-12-06 12:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-06 11:58 Git Books Scott Chacon
2008-12-06 12:09 ` Thomas Adam [this message]
2008-12-06 12:27 ` Christian MICHON
2008-12-06 13:39   ` Dilip M
2008-12-06 12:54 ` Jakub Narebski
2008-12-06 14:38   ` nadim khemir
2008-12-06 12:56 ` Paolo Ciarrocchi
2008-12-06 19:45 ` Björn Steinbrink
2008-12-06 23:48   ` Deskin Miller

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=18071eea0812060409y33680534p6b9ad56dd5043538@mail.gmail.com \
    --to=thomas.adam22@gmail.com \
    --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).