|Fwd: Re: is git.auto.fetch implemented at all? [message #1691054]
||Wed, 01 April 2015 21:46
| Ed Willink
Registered: July 2009
-------- Forwarded Message --------|
Subject: Re: is git.auto.fetch implemented at all?
Date: Wed, 05 Nov 2014 17:13:21 +0000
From: Ed Willink <firstname.lastname@example.org>
Ping. Anyone able to comment?
On 05/10/2014 16:16, Ed Willink wrote:
> What is the status of this?
> I appear to need to delete my Hudson Workspace to get a GIT 'refresh'.
> Searching comes up with this correspondence.
> On my Hudson HIPP I appear to have only the choice of Buckminster 4.2 so
> perhaps 4.3 or 4.4 may have already fixed it.
> But when I look at
> I see that the current version of Buckminster is 2.0.0 perhaps released
> 18 months ago but if so without a release review. No plans for further
> I'm really confused. What is the best Buckminster version and does it
> fix the GIT refresh problem?
> Ed Willink
> On 28/01/2014 09:06, Lorenzo Bettini wrote:
>> On 20/01/2014 14:04, Thomas Hallgren wrote:
>>> On 2014-01-02 19:21, Lorenzo Bettini wrote:
>>>> Is git.auto.fetch considered during materialization?
>>> Not really. That functionality was written as part of the first
>>> incarnation of the git support feature. I didn't know enough about git
>>> to do a proper evaluation for a requirement spec. My current
>>> recommendation would be to not use it. If someone has the time to look
>>> into how this should be implemented properly, then I'd be very
>>> interested in reviewing a patch. One thing that comes to mind
>>> immediately is that the auto.fetch should be called auto.pull (since
>>> that's what it was intended as).
>> OK, I'll submit a bug and see whether I can come up with something :)
Powered by FUDForum
. Page generated in 0.01869 seconds