From: Michael Witten <mfwitten@gmail.com>
To: Peter Kleiweg <pkleiweg@xs4all.nl>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jeff King" <peff@peff.net>,
git@vger.kernel.org
Subject: Re: file mode
Date: Tue, 14 Jun 2011 05:51:06 -0000 [thread overview]
Message-ID: <ea0263ba89684f958d91bbf1fa2dcdc6-mfwitten@gmail.com> (raw)
In-Reply-To: <BANLkTimgby8-aBmXiZ72vtxoLO6Tr7zi2g@mail.gmail.com>
On Mon, 13 Jun 2011 23:18:58 +0200, Ævar Arnfjörð Bjarmason wrote:
>> On Mon, Jun 13, 2011 at 05:38, Jeff King <peff@peff.net> wrote:
>>> 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?
>>
>> No.
>>
>> Firstly: My response shows that there are abundant answers, which is a
>> nicer answer to receive than no answer at all.
>>
>> Secondly: I didn't see the point in RE-WRITING all that has been said
>> on the subject before, and I couldn't be sure that somebody else would
>> be willing to do the same too (I figured it was a good idea to supply
>> at least one response).
>>
>> Thirdly: Seriously, at least do some googling first.
>
> I think having answers like yours is much worse than having no answer
> at all. I happen to know how git handles the storage of file
> permissions, but like Jeff I couldn't find anything useful either with
> some quick searching around.
>
> But it's very useful that the list have a friendly atmosphere where
> people of different technical capability, or those that haven't found
> the right terms to feed into a search engine can ask questions without
> getting back an answer which at least to me seems very snarky.
>
> There's a tendency in a lot of mailing list to accumulate a
> self-congratulating air from regulars "in the know" where people
> asking questions aren't made to feel welcome. Let's try to not become
> one of those lists.
Peter Kleiwig, I would be most grateful if you could find it in your heart
to forgive a poor, misguided, mutton-faced, thistle-bottomed, pig-swiving,
ale-soused dungball such as myself.
This wretch, I, humbly prostrates himself before the feet of the offended
in earnest compunction over his unconscionably uncouth utterances; may I
next time guard my tongue or, if finding myself unequal to that task, be
so thoughtful as to bite it off, preserve it for at least a year and a day
in a barrel of briny liquid most foul, and then—on the coldest day of
winter—dispense with it as fodder for the hunger pangs of feral cats!
next prev parent reply other threads:[~2011-06-14 6:16 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
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 [this message]
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=ea0263ba89684f958d91bbf1fa2dcdc6-mfwitten@gmail.com \
--to=mfwitten@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--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).