Date: Thu, 19 Nov 2020 12:45:14 -0500 From: Dan Langille <dan@langille.org> To: Mathieu Arnold <mat@FreeBSD.org> Cc: freebsd-git@freebsd.org Subject: Re: Monitoring commits on all branches Message-ID: <EF8F4764-3C26-4BAB-9B1E-E0686A675E20@langille.org> In-Reply-To: <20201119085223.nsrp2e45oyepsvds@aching.in.mat.cc> References: <197541CC-FEA7-4B4C-936E-66A5625BB64C@langille.org> <20201119085223.nsrp2e45oyepsvds@aching.in.mat.cc>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Nov 19, 2020, at 3:52 AM, Mathieu Arnold <mat@FreeBSD.org> wrote: >=20 > On Wed, Nov 18, 2020 at 08:49:46PM -0500, Dan Langille wrote: >> How can a repo be monitored for commits on all branches? >>=20 >> I know how to ask a given branch: do you have any commits after = foo_hash? >>=20 >> How do I: >>=20 >> * get a list of all commits since foo_hash >=20 > All commits on the branch foo_hash is: >=20 > git log $foo_hash...branch_name So, branch_name, not HEAD as others have mentioned? e.g. : git log $foo_hash..HEAD >=20 >> * know which branch each of those commits was on (e.g. master, = branches/2020Q4) >=20 > You will need to keep track of the latest commit on each branch > separately, because there is absolutely no relation or ordering > possible between branches. Yes, I agree. FreshPorts is keeping track of the last commit on each = branch. Thank you.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EF8F4764-3C26-4BAB-9B1E-E0686A675E20>