From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: Jeff King <peff@peff.net>
Cc: Michael Witten <mfwitten@gmail.com>,
Peter Kleiweg <pkleiweg@xs4all.nl>,
git@vger.kernel.org
Subject: Re: file mode
Date: Mon, 13 Jun 2011 15:52:52 +0200 [thread overview]
Message-ID: <4DF61634.7020003@dirk.my1.cc> (raw)
In-Reply-To: <20110613053814.GA2680@sigill.intra.peff.net>
Am 13.06.2011 07:38 schrieb Jeff King:
> On Sun, Jun 12, 2011 at 07:12:42PM +0000, Michael Witten wrote:
>
>> On Sun, Jun 12, 2011 at 18:57, Peter Kleiweg <pkleiweg@xs4all.nl> wrote:
>>> I added a file that has file mode 600. When I do a check-out,
>>> the file comes with mode 644. Is this supposed to happen? Then
>>> how do I control what permissions files have?
>>
>> Do some googling.
>
> I really don't see the point of a response like this. It is one thing to
> rudely point somebody to lmgtfy or an FAQ link. Then you're still being
> rude, but at least you are pointing them in the right direction. But
> this seems simply to make the list a less pleasant place _and_ to be
> totally useless to the original poster. If you didn't want to give the
> answer, wouldn't it have been better not to respond at all?
>
My sentiments exactly. Actually this list is one of the best I ever met
or subscribed to. Even posts with the meaningless subject "Help needed"
are answered. I've seen some of them. Few, though. Please, people, stick
to what Peff suggests. I think for most newbees this list is the last
effort AFTER googling, so googling won't help.
Cheers,
Dirk
next prev parent reply other threads:[~2011-06-13 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-12 18:57 file mode Peter Kleiweg
2011-06-12 19:12 ` Michael Witten
2011-06-13 5:38 ` Jeff King
2011-06-13 13:52 ` Dirk Süsserott [this message]
2011-06-13 13:58 ` Michael Witten
2011-06-13 13:58 ` Michael Witten
2011-06-13 21:18 ` Ævar Arnfjörð Bjarmason
2011-06-14 5:51 ` Michael Witten
2011-06-13 14:25 ` Peter Kleiweg
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=4DF61634.7020003@dirk.my1.cc \
--to=newsletter@dirk.my1.cc \
--cc=git@vger.kernel.org \
--cc=mfwitten@gmail.com \
--cc=peff@peff.net \
--cc=pkleiweg@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).