On Mon, 8 Aug 2016, Jeff King wrote:
> On Fri, Aug 05, 2016 at 04:19:08PM +0200, Johannes Schindelin wrote:
> > > The fix is meant for jk/push-force-with-lease-creation topic, but I
> > > had to find it out by the old fashioned way, i.e. running blame for
> > > these lines in 'pu' to find eee98e74f9 is the culprit and then
> > > running "git branch --with eee98e74f9". The only thing the line
> > > made easier is I _could_ start the blame at the named commit (which
> > > is on 'next') instead of 'pu'. When I took that "base-commit"
> > > series, I was hoping that it would give us a lot more useful
> > > information.
> > Sorry for that. The way my mail-patch-series.sh script works is that
> > it tries to determine which branch between `master`, `next` or `pu` is
> > the base (and it then submits *all* commits that are on top of that
> > branch).
> > So my branch was indeed based on `next` for that reason, not on top of
> > `jk/push-force-with-lease-creation`. Otherwise, I would have
> > resubmitted John's patches because the script would have determined
> > that my patch is on top of `master`, not on top of `next`.
> Do you fetch from the main git.git repository, or Junio's gitster/git
> workspace on GitHub?
Neither. I typically fetch from https://github.com/git/git.
Even so, I can in general find out relatively easily what commit is the
tip of the branch I am looking for.
In this here case, I was just too lazy (or too busy with other stuff,
depending on your point of view), is all ;-)
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html