From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Clean generated files a bit more.
Date: Fri, 12 Aug 2005 06:55:53 -0700 [thread overview]
Message-ID: <7vpssj1cpi.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050812114053.GB29893@pasky.ji.cz> (Petr Baudis's message of "Fri, 12 Aug 2005 13:40:53 +0200")
Petr Baudis <pasky@suse.cz> writes:
> This makes me a bit nervous - why are you making the rules more general?
> make clean removing random tarballs of mine happenning to dwell in that
> directory is fearsome.
That is a valid concern. I'd drop that *.tar.gz part at
least and probably the *.deb *.dsc part as well. Thanks for
sanity checking.
prev parent reply other threads:[~2005-08-12 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-12 9:41 [PATCH] Clean generated files a bit more Junio C Hamano
2005-08-12 11:40 ` Petr Baudis
2005-08-12 13:55 ` Junio C Hamano [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=7vpssj1cpi.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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