From: Junio C Hamano <junkio@cox.net>
To: "Andreas Jellinghaus [c]" <aj@dungeon.inka.de>
Cc: git@vger.kernel.org, Ryan Anderson <ryan@michonline.com>
Subject: Re: [PATCH] debian/ binary package dependency fix. [u]
Date: Mon, 25 Jul 2005 09:27:09 -0700 [thread overview]
Message-ID: <7vek9mrgv6.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200507251052.37618.aj@dungeon.inka.de> (Andreas Jellinghaus's message of "Mon, 25 Jul 2005 10:52:37 +0200")
"Andreas Jellinghaus [c]" <aj@dungeon.inka.de> writes:
> rsync should be Recommended: or Suggested: only,
> as git can be used local only as well, and then
> rsync is not needed, right?
I suspect we still use rsync even in some local cases (rsync
between two local directories). At least we once used to and I
do not remeber touching that piece of code..
prev parent reply other threads:[~2005-07-25 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 6:27 [PATCH] debian/ binary package dependency fix Junio C Hamano
2005-07-25 8:52 ` [PATCH] debian/ binary package dependency fix. [u] Andreas Jellinghaus [c]
2005-07-25 16:27 ` 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=7vek9mrgv6.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=aj@dungeon.inka.de \
--cc=git@vger.kernel.org \
--cc=ryan@michonline.com \
/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