*** pacon has joined #baserock | 00:43 | |
*** zoli__ has joined #baserock | 01:58 | |
*** zoli__ has quit IRC | 02:03 | |
*** zoli__ has joined #baserock | 04:13 | |
*** zoli___ has joined #baserock | 04:22 | |
*** zoli__ has quit IRC | 04:22 | |
*** zoli___ has quit IRC | 04:37 | |
* paulsherwood discovers that ybd seems to be the first tool to need unpetrify-ref | 06:53 | |
paulsherwood | bah. my br vm can't access network via my usb-connected phone | 08:45 |
---|---|---|
*** zoli__ has joined #baserock | 08:49 | |
*** zoli__ has quit IRC | 08:55 | |
* paulsherwood notices we've misspelled daemon in DLT-deamon :/ | 09:11 | |
*** pacon has quit IRC | 11:16 | |
*** pacon has joined #baserock | 11:19 | |
*** pacon has quit IRC | 11:23 | |
*** pacon has joined #baserock | 11:24 | |
*** pacon has quit IRC | 11:43 | |
*** pacon has joined #baserock | 11:45 | |
*** pacon has quit IRC | 11:48 | |
*** pacon has joined #baserock | 11:49 | |
*** pacon has quit IRC | 12:24 | |
persia | For what does ybd use unpetrify-ref? | 14:01 |
paulsherwood | i'm trying --depth 1' to speed up initial user start. as a result it seems i need to do 'git fetch --depth 1000000 this['unpetrify-ref']' in the case where current SHA has not been found at tip of any branch | 19:01 |
paulsherwood | s/trying/trying 'git clone / | 19:01 |
paulsherwood | this is working, but showed (in definitions master) one example of 'unpretrify-ref' and one example of no field at all so far | 19:03 |
persia | git clone should work with a SHA1 that is not the tip of any branch. | 19:08 |
paulsherwood | in an existing clone? | 19:08 |
persia | git fetch has a documented bug about the use of SHA1s | 19:08 |
paulsherwood | yup, understood. my use-case is git submodule - eg gstreamer requires a non-tip checkout of gstreamer-common. i've already cloned gstreamer-common to calculate cache-key | 19:10 |
persia | But I think git fetch will break with submodules even with that use of unpetrify-ref | 19:10 |
paulsherwood | no, it seems to be working | 19:10 |
persia | Docs say "Using --recurse-submodules can only fetch new commits in already checked out submodules right now. When e.g. upstream added a new submodule in the just fetched commits of the superproject the submodule itself can not be fetched, making it impossible to check out that submodule later without having to do a fetch again. This is expected to be fixed in a future Git version." | 19:11 |
paulsherwood | i'm fetching into the pre-existing --depth 1 clones /src/cache/gits | 19:11 |
paulsherwood | sadly i can't push my code... my br vm doesn't like airport networks | 19:12 |
persia | That so many tools have such a dependence on high quality networks is a major failing with this particular toolset. | 19:13 |
persia | I am routinely in locations where everything doesn't work. I recommend not using a VM on your laptop: using remote VMs somewhere seems a bit more stable. | 19:13 |
paulsherwood | fair point. but i'm developing locally on planes, too, with no network at all. ybd works pretty well for that use-case, once gits are pre-loaded | 19:14 |
paulsherwood | but maybe this 'optimisation' will weaken that | 19:15 |
persia | Very much so. | 19:15 |
paulsherwood | i'll ponder, on my next flight :) | 19:16 |
persia | As long as you have sufficiently deep clones for useful development of the trees that you need to modify, you will be fine. | 19:19 |
paulsherwood | it's hard to know what that depth would be, though | 19:24 |
persia | I find that I rarely need to review history more than about a decade, but that might just be me. | 19:39 |
paulsherwood | :) | 19:40 |
paulsherwood | depth is nubmer of commits, though, not time. | 19:40 |
persia | I doubt there are useful heuristics. Of the projects that I know that are more than 20 years old, some get an average of a commit a day, and others get an average of 100 commits a day. | 19:56 |
paulsherwood | yup | 20:02 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!