Date: Wed, 18 Nov 2020 19:18:07 -0700 From: Warner Losh <imp@bsdimp.com> To: Dan Langille <dan@langille.org> Cc: freebsd-git@freebsd.org Subject: Re: Monitoring commits on all branches Message-ID: <CANCZdfqvk415oGDcq7_g8C=d9N-i1vLgCvd=wCAwKS5dNEFLPg@mail.gmail.com> In-Reply-To: <197541CC-FEA7-4B4C-936E-66A5625BB64C@langille.org> References: <197541CC-FEA7-4B4C-936E-66A5625BB64C@langille.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 18, 2020, 6:49 PM Dan Langille <dan@langille.org> wrote: > How can a repo be monitored for commits on all branches? > > I know how to ask a given branch: do you have any commits after foo_hash? > > How do I: > > * get a list of all commits since foo_hash > git log $hash..HEAD will list all the commits on the branch. Between branches 'since' has little to no meaning. * know which branch each of those commits was on (e.g. master, > branches/2020Q4) > You need to know which branches are interesting. There are some git log options... --date-order might help since dates are weird in git... All of this is a consequence of git being distributed. Warner Thanks. > > -- > Dan Langille - BSDCan / PGCon > dan@langille.org > > > _______________________________________________ > freebsd-git@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-git > To unsubscribe, send any mail to "freebsd-git-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqvk415oGDcq7_g8C=d9N-i1vLgCvd=wCAwKS5dNEFLPg>