On Thu, Oct 4, 2018 at 8:55 AM Kaartic Sivaraam
wrote:
>
>
>
> On 3 October 2018 00:13:06 GMT+05:30, Kaartic Sivaraam
> wrote:
> >Hi,
> >
> >Sorry for the delay. Got a little busy over the weekend. I seem to have
> >found the reason behind the issue in the mean time :-)
> >
>
> Oops, I forgot
On 3 October 2018 00:13:06 GMT+05:30, Kaartic Sivaraam
wrote:
>Hi,
>
>Sorry for the delay. Got a little busy over the weekend. I seem to have
>found the reason behind the issue in the mean time :-)
>
Oops, I forgot to mention there's more comments inline!
BTW, is there an issue if .git/HEAD
Hi,
Sorry for the delay. Got a little busy over the weekend. I seem to have
found the reason behind the issue in the mean time :-)
On Wed, 2018-09-26 at 10:05 -0700, Junio C Hamano wrote:
> Duy Nguyen writes:
>
> > On Wed, Sep 26, 2018 at 05:24:14PM +0200, Duy Nguyen wrote:
> > > On Wed, Sep
Duy Nguyen writes:
> On Wed, Sep 26, 2018 at 05:24:14PM +0200, Duy Nguyen wrote:
>> On Wed, Sep 26, 2018 at 6:46 AM Kaartic Sivaraam
>> wrote:
>> > This is the most interesting part of the issue. I **did not** run
>> >'git fetch ...' in between those cat commands. I was surprised by
>> >how the
On Wed, Sep 26, 2018 at 05:24:14PM +0200, Duy Nguyen wrote:
> On Wed, Sep 26, 2018 at 6:46 AM Kaartic Sivaraam
> wrote:
> > This is the most interesting part of the issue. I **did not** run
> >'git fetch ...' in between those cat commands. I was surprised by
> >how the contents of FETCH_HEAD are
On Wed, Sep 26, 2018 at 6:46 AM Kaartic Sivaraam
wrote:
> This is the most interesting part of the issue. I **did not** run 'git fetch
> ...' in between those cat commands. I was surprised by how the contents of
> FETCH_HEAD are changing without me spawning any git processes that might
>
Hi,
I just wanted make a point a little more clear. See comment inline.
On 24 September 2018 01:39:26 GMT+05:30, Kaartic Sivaraam
wrote:
> To add to that
>confusion when I run
>
> $ cat $MAIN_WORKTREE/.git/worktrees/$BUILD_WORKTREE/FETCH_HEAD
>
>it seems to be printing the info about the
On 26 September 2018 03:10:17 GMT+05:30, Junio C Hamano
wrote:
>
> That looks like fetching only the 'next' branch and nothing else to
> me.
>
Interesting.
> Perhaps your script is referring to a variable whose assignment is
> misspelled and invoking
>
> git fetch $origin $branch
>
Kaartic Sivaraam writes:
>> Also please try
>> "git fetch" again with GIT_TRACE=1 and GIT_TRACE_SETUP=1. Hopefully we
>> could catch something with that.
>
> $ GIT_TRACE_SETUP=1 GIT_TRACE=1 git fetch origin next
> 23:10:26.049785 trace.c:377 setup: git_dir:
>
On Mon, 2018-09-24 at 17:17 +0200, Duy Nguyen wrote:
> On Sun, Sep 23, 2018 at 10:19 PM Kaartic Sivaraam
> wrote:
>
> Yes, some bugs. It behaves correctly for me. There must be something
> strange that triggers this. What's your "git worktree list" (iow
> anything strange there, duplicate
On Sun, Sep 23, 2018 at 10:19 PM Kaartic Sivaraam
wrote:
>
> Hi,
>
> I was actually trying to automae the building and installation of Git
> source code to reduce my burden. I tried to automate it with the help
> of a script that runs daily via cron and a separate worktree used only
> by the
Hi,
I was actually trying to automae the building and installation of Git
source code to reduce my burden. I tried to automate it with the help
of a script that runs daily via cron and a separate worktree used only
by the build script.y run
The script typically fetches new changes for the next
12 matches
Mail list logo
