From: Michael Witten <mfwitten@MIT.EDU>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>
Subject: Re: Imports without Tariffs
Date: Sun, 14 Oct 2007 18:10:50 -0400 [thread overview]
Message-ID: <7B69C0EA-A1FB-4133-895E-AE30DBAECC11@MIT.EDU> (raw)
In-Reply-To: <20071014164001.GC27595@sigill.intra.peff.net>
On 14 Oct 2007, at 12:40:01 PM, Jeff King wrote:
> On Sat, Oct 13, 2007 at 07:04:52PM -0400, Michael Witten wrote:
>> Do I just submit the patch to this list? How do I know it will be
>> used?
>
> Yes, send a patch to the list and to Junio (the maintainer). See
> Documentation/SubmittingPatches for details.
Indeed! RTFM, as they say. ;-)
>> Frankly, I don't know how robust my idea is either, but it's simple
>> enough not to have many problems lurking in the shadows.
>>
>> It would certainly be more useful than not.
>
> Then submit a patch implementing it. :)
Perl. Ugh. I'll see what I can do, though it may take 1.5 weeks.
> I like the idea of git secretly infiltrating institutions,
> replacing CVS unbeknownst to management. It was the same for Linux in
> the mid-90's ("our mail server is running on what!?").
:-)
Replace CVS or Bust!
next prev parent reply other threads:[~2007-10-14 22:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-13 4:01 (unknown), Michael Witten
2007-10-13 4:07 ` your mail Jeff King
[not found] ` <1240801C-F4CC-4290-8C3D-2038F1957DF3@MIT.EDU>
2007-10-13 4:39 ` Imports without Tariffs Michael Witten
2007-10-13 7:57 ` Jeff King
2007-10-13 23:04 ` Michael Witten
2007-10-14 16:40 ` Jeff King
2007-10-14 22:10 ` Michael Witten [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-12 20:36 mfwitten
2007-10-13 2:49 ` Jeff King
[not found] ` <3B7796D6-5901-40B0-B3FC-70642AC50B08@mit.edu>
2007-10-13 4:44 ` Michael Witten
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=7B69C0EA-A1FB-4133-895E-AE30DBAECC11@MIT.EDU \
--to=mfwitten@mit.edu \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).