From: Stefan Sperling Subject: Re: fix missed doc update of new 'got fetch' behaviour To: Mark Jamsek Cc: Game of Trees Date: Fri, 3 Feb 2023 08:18:45 +0100 On Fri, Feb 03, 2023 at 03:48:58PM +1100, Mark Jamsek wrote: > As per the subject, we need to update the -a doc for the change in 'got > fetch' behaviour: Yes, sure. > > ----------------------------------------------- > commit 503168c5866afbbe0243bcdddc2c0e769e71af05 (main) > from: Mark Jamsek > date: Fri Feb 3 04:40:09 2023 UTC > > fix missed doc update of new 'got fetch' behaviour > > diff f1d971f3ed617e4e24f33119d2c35671178d860f 503168c5866afbbe0243bcdddc2c0e769e71af05 > commit - f1d971f3ed617e4e24f33119d2c35671178d860f > commit + 503168c5866afbbe0243bcdddc2c0e769e71af05 > blob - ff51dcada6ea9946aed98884cc5f0bdaa65a5164 > blob + 2f2d51be710c9d1ff0291d1284b33f43eb85e145 > --- got/got.1 > +++ got/got.1 > @@ -383,8 +383,10 @@ If this option is not specified, a branch resolved via > reference namespace. > This option can be enabled by default for specific repositories in > .Xr got.conf 5 . > -If this option is not specified, a branch resolved via the remote > -repository's HEAD reference will be fetched. > +If this option is not specified, the work tree's current branch > +will be fetched if invoked within a work tree, > +otherwise a branch resolved via the remote repository's HEAD reference > +will be fetched. > Cannot be used together with the > .Fl b > option. > > -- > Mark Jamsek > GPG: F2FF 13DE 6A06 C471 CA80 E6E2 2930 DC66 86EE CF68