From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Do we still do Incoming* files?
Date: 20 Apr 2000 20:45:18 +0200 [thread overview]
Message-ID: <m3aeio7gsh.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <vxkaejx5oq3.fsf@mesquite.charcoal.com>
Karl Kleinpaste <karl@charcoal.com> writes:
> Lars will have to be convinced to turn on -delete-incoming only when
> creating released tarballs, so that it is always nil in CVS.
>
> I'm not convinced that this is a Good Thing.
Mee too. I've now changed the default.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2000-04-20 18:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-17 18:40 lconrad
2000-03-17 19:09 ` Kai Großjohann
2000-03-17 19:23 ` lconrad
2000-03-17 19:51 ` Karl Kleinpaste
2000-03-17 19:17 ` Karl Kleinpaste
2000-03-17 20:00 ` Kai Großjohann
2000-03-17 20:24 ` Karl Kleinpaste
2000-03-17 20:53 ` Kai Großjohann
2000-03-17 21:28 ` lconrad
2000-03-17 21:44 ` Kai Großjohann
2000-03-17 22:07 ` lconrad
2000-03-17 22:13 ` Gunnar Evermann
2000-03-17 22:59 ` Kai Großjohann
2000-03-17 23:07 ` lconrad
2000-03-18 4:01 ` Harry Putnam
2000-04-20 18:45 ` Lars Magne Ingebrigtsen [this message]
2000-03-17 23:54 Laura Conrad
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=m3aeio7gsh.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/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).