From: Sitaram Chamarty <sitaramc@gmail.com>
To: gitster@pobox.com, git@vger.kernel.org
Subject: [PATCH] Remove obsolete bug warning in man git-update-server-info
Date: Sat, 25 Apr 2009 16:26:52 +0530 [thread overview]
Message-ID: <20090425105652.GA16297@atcmail.atc.tcs.com> (raw)
The bug referred to was fixed in 60d0526
Signed-off-by: Sitaram Chamarty <sitaramc@gmail.com>
---
It was fixed in September 2005 [thanks to drizzd on irc for
pointing this out].
I'd also make a plea for someone who groks this better than
I do to document what --force does and under what conditions
it may be needed; the code looks to me like parse_pack_def
should take care of the problem, but clearly it was needed
for some reason that I'm not expert enough to understand.
Documentation/git-update-server-info.txt | 6 ------
1 files changed, 0 insertions(+), 6 deletions(-)
diff --git a/Documentation/git-update-server-info.txt b/Documentation/git-update-server-info.txt
index 35d27b0..035cc30 100644
--- a/Documentation/git-update-server-info.txt
+++ b/Documentation/git-update-server-info.txt
@@ -39,12 +39,6 @@ what they are for:
* info/refs
-BUGS
-----
-When you remove an existing ref, the command fails to update
-info/refs file unless `--force` flag is given.
-
-
Author
------
Written by Junio C Hamano <gitster@pobox.com>
--
1.6.2
reply other threads:[~2009-04-25 11:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090425105652.GA16297@atcmail.atc.tcs.com \
--to=sitaramc@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).