From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15351 invoked by alias); 9 Nov 2013 22:52:44 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 31946 Received: (qmail 23614 invoked from network); 9 Nov 2013 22:52:40 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 Date: Sat, 9 Nov 2013 17:52:38 -0500 From: Aaron Schrab To: zsh workers Subject: Re: Can we all quietly agree to fix this commit log? Message-ID: <20131109225238.GC6807@pug.qqx.org> Mail-Followup-To: zsh workers References: <131108182028.ZM26321@torch.brasslantern.com> <131109142302.ZM27202@torch.brasslantern.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <131109142302.ZM27202@torch.brasslantern.com> User-Agent: Mutt/1.5.22+36 (g7db327c) (2013-10-16) At 14:23 -0800 09 Nov 2013, Bart Schaefer wrote: >Given the tagging issue, I don't think Wayne's suggestion is quite what >I was hoping for. Aaron's is a bit more like it. > >If the "git replace" were pushed, would new clones see it, or would it >always be necessary to explicitly fetch the replacement refs? The replacement refs would always need to be fetched explicitly. Doing a clone is basically just setting up a new local repository, adding a remote to it (including the default refspec that will be used for fetching), and then a fetch like any other fetch. So the replacement refs wouldn't show up there either. The only way to fix this type of issue without everybody who uses the repository needing to take some action would be to rewrite the history.