On 06/11, Christian Couder wrote:
> On Sat, Jun 10, 2017 at 9:05 PM, Kevin Daudt wrote:
> > On Sat, Jun 10, 2017 at 02:48:36PM +0200, Kevin Daudt wrote:
>
> >> For me, this bisects to the latest merge:
> >>
> >> 2047eebd3 (Merge branch 'bw/repo-object' into pu, 2017-06-10), but
> >> neither of th
On Sat, Jun 10, 2017 at 9:05 PM, Kevin Daudt wrote:
> On Sat, Jun 10, 2017 at 02:48:36PM +0200, Kevin Daudt wrote:
>> For me, this bisects to the latest merge:
>>
>> 2047eebd3 (Merge branch 'bw/repo-object' into pu, 2017-06-10), but
>> neither of the parent of the merge break this test, so it loo
On Sat, Jun 10, 2017 at 02:48:36PM +0200, Kevin Daudt wrote:
> On Sat, Jun 10, 2017 at 03:07:01PM +0900, Junio C Hamano wrote:
> > I didn't check where it goes wrong. Here is a list of suspects,
> > taken by
> >
> > $ git shortlog --no-merges pu@{8.hours}..pu
> >
> > i.e. patches that weren'
On Sat, Jun 10, 2017 at 03:07:01PM +0900, Junio C Hamano wrote:
> I didn't check where it goes wrong. Here is a list of suspects,
> taken by
>
> $ git shortlog --no-merges pu@{8.hours}..pu
>
> i.e. patches that weren't in pu before today's integration cycle.
>
> Andreas Heiduk (1):
>
I didn't check where it goes wrong. Here is a list of suspects,
taken by
$ git shortlog --no-merges pu@{8.hours}..pu
i.e. patches that weren't in pu before today's integration cycle.
Andreas Heiduk (1):
doc: describe git svn init --ignore-refs
Brandon Williams (32):
config: cre
5 matches
Mail list logo