git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Francesco Pretto <ceztkoml@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: enhanced "git for CVS users" doc about shared repositories
Date: Wed, 07 Nov 2007 01:46:07 +0100	[thread overview]
Message-ID: <47310ACF.4030103@gmail.com> (raw)
In-Reply-To: <7vd4unez2l.fsf@gitster.siamese.dyndns.org>

Junio C Hamano ha scritto:
> 
> Honestly speaking, I am not too thrilled about making the
> cvs-migration document much longer than what it currently is.
> 

Honestly speaking, you've spent too much time in looking for every possible
objections against these simple additions. At least it should be less than the
time I've spent in measuring every single word of this patch, hoping you could
consider them for inclusion. You gave me lot of attentions (I am grateful of this,
really) so I should probably be surprised of the cleanliness of git code, of the
rigor of the code style, of the clarity of the documentation. But unfortunately,
I am not. I simply tried to make this document more useful and helpful for a
wider audience of people that could ever consider of using git in their life.
And yes, I decided to so because I had trouble myself during initial configurations.
What's the problem if a document called "git for CVS users" is more explicated?
What's the problem if it contains as many as possible informations to set up
git in a viable way and, hopefully, to learn something on how it does work?

I'm sad. Not only because you refused a documentation patch, but because i could
have sent a "Bug: Documentation Sucks!" to the ml and i would have obtained the
same thing: nothing.

Francesco

P.S.:

>> +------------------------------------------------
>> +$ usermod -a -G $group $username
>> +------------------------------------------------
> 
> I tend to edit /etc/group with vi ;-) and I suspect these two
> commands are specific to the distro you happen to use.

You were right with usermod (groupadd is ok): that "-a" switch is redhat syntax.
Six years of Linux Standard Base and this is still an unsolved problem...

  reply	other threads:[~2007-11-07  0:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05 22:32 [Patch] Documentation: enhanced "git for CVS users" doc about shared repositories Francesco Pretto
2007-11-05 23:52 ` Junio C Hamano
2007-11-06 10:04   ` Francesco Pretto
2007-11-06 10:53     ` Johannes Schindelin
2007-11-06 11:14       ` Francesco Pretto
2007-11-06 21:44   ` [PATCH] " Francesco Pretto
2007-11-06 23:25     ` Junio C Hamano
2007-11-07  0:46       ` Francesco Pretto [this message]
2007-11-07  0:55         ` Johannes Schindelin
2007-11-07  1:10           ` Francesco Pretto
2007-11-07  1:36           ` Aghiles
2007-11-07  7:35             ` Steffen Prohaska
2007-11-07  8:45               ` Andreas Ericsson
2007-11-07  9:09           ` David Kastrup
2007-11-07 17:32           ` J. Bruce Fields
2007-11-07  8:03         ` Wincent Colaiuta
2007-11-07  8:07         ` Steffen Prohaska
2007-11-07 16:47           ` 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=47310ACF.4030103@gmail.com \
    --to=ceztkoml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).