From: Thomas Rast <trast@student.ethz.ch>
To: Thomas Ackermann <th.acker@arcor.de>
Cc: <git@vger.kernel.org>
Subject: Re: Aw: [PATCH 0/2] GIT, Git, git
Date: Sun, 20 Jan 2013 12:56:37 +0100 [thread overview]
Message-ID: <87d2x0xe2y.fsf@pctrast.inf.ethz.ch> (raw)
In-Reply-To: <304952858.714413.1358671123163.JavaMail.ngmail@webmail06.arcor-online.net> (Thomas Ackermann's message of "Sun, 20 Jan 2013 09:38:43 +0100 (CET)")
Thomas Ackermann <th.acker@arcor.de> writes:
>> Git changed its 'official' system name from 'GIT' to 'Git' in v1.6.5.3
>> (as can be seen in the corresponding release note where 'GIT' was
>> changed to 'Git' in the header line).
>>
>> Alas the documention uses 'GIT', 'Git' or even 'git' to refer to the
>> Git system. So change every occurrence of 'GIT" and 'git' to 'Git'
>> whenever Git as a system is referred to (but don't do this change
>> in the release notes because they constitute a history orthogonal
>> to the history versioned by Git).
>>
>> [PATCH 1/2] Change old system name 'GIT' to 'Git'
>> [PATCH 2/2] Change 'git' to 'Git' whenever the whole system is referred to
>>
>
> My second patch somehow got lost in the mailing system (I suspect
> due to its size of >300kB). I will wait for some more comments
> and then do a reroll thereby splitting the second patch in smaller
> parts ...
For such big patches it also helps if you push them somewhere public,
and post the URL and branch name, so that interested parties can still
have a look.
But yes, vger.kernel.org silently discards all mail above 100KB, see
http://vger.kernel.org/majordomo-info.html
in the last section.
--
Thomas Rast
trast@{inf,student}.ethz.ch
prev parent reply other threads:[~2013-01-20 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 8:38 Aw: [PATCH 0/2] GIT, Git, git Thomas Ackermann
2013-01-20 11:56 ` Thomas Rast [this message]
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=87d2x0xe2y.fsf@pctrast.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=th.acker@arcor.de \
/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).