Hi Junio,
On Sun, Feb 21, 2016 at 08:19:56PM -0800, Junio C Hamano wrote:
> Xiaolong Ye writes:
>
> > It would be helpful for maintainers or reviewers to know the base tree
> > info of the patches created by git format-patch. Teach git format-patch
> > a --base-tree-info option to record these i
Hi Junio and All,
CC more relevant people. FYI this thread starts here:
http://thread.gmane.org/gmane.comp.version-control.git
On Mon, Feb 22, 2016 at 10:54:38PM -0800, Junio C Hamano wrote:
> Fengguang Wu writes:
>
> > Hi Junio,
> >
> > On Sun, Feb 21, 2016 at
On Tue, Feb 23, 2016 at 01:23:19AM -0800, H. Peter Anvin wrote:
> On 02/23/16 01:17, Fengguang Wu wrote:
> >
> > However we are facing a new situation: in test robot POV, IMHO there
> > are values to test exactly the same tree as the patch submitter.
> > Otherwise the r
Hi Dan,
On Tue, Feb 23, 2016 at 01:32:53PM +0300, Dan Carpenter wrote:
> So this is the format for the first patch?
>
> base commit: 0233b800c838ddda41db318ee396320b3c21a560
What's in my mind is lines like
base tree/branch:
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git maste
Hi Eric,
On Tue, Feb 23, 2016 at 01:56:07PM -0600, Eric W. Biederman wrote:
>
> Fengguag Wu, Xiaolong Ye, have you attempted to use the truncated
> sha1 of the file the patch applies to? Git already places a file sha1
> at the top of a patch. See the index line?
>
> > diff --git a/fs/namespace
On Tue, Feb 23, 2016 at 04:31:35PM +0300, Dan Carpenter wrote:
> Blergh... You want it machine readable and I want it human readable. I
Yeah. It's kind of tasting which may differ among people. I'll leave
the judgments to Junio and others, and only add necessary comments to
your points.
> don't
On Tue, Feb 23, 2016 at 11:51:31AM -0800, Junio C Hamano wrote:
> Fengguang Wu writes:
>
> >> >> I have a mixed feeling about this one, primarily because this was
> >> >> already tried quite early in the life of "format-patch" command.
> &g
On Tue, Feb 23, 2016 at 12:35:12PM -0800, Junio C Hamano wrote:
> ebied...@xmission.com (Eric W. Biederman) writes:
>
> > Junio C Hamano writes:
> >
> >> It is valuable for a testing organization to say "We tested this
> >> series on top of version X. We know it works, we have tested on a
> >> l
On Tue, Feb 23, 2016 at 10:30:04PM -0800, Junio C Hamano wrote:
> Fengguang Wu writes:
>
> > The necessary lines for the robot are
> >
> > base commit:
> > base patch-id:
> > or
> > base tree-id:
> > base patch-id:
> > I don't know how 0 bot solves this, but the obvious issue with this
> > approach is to allow dealing with someone sending a patch like
> >
> > +++ Makefile
> > --- Makefile
> > +all:
> > + rm -fr $(HOME); sudo rm -fr /
> >
> > to the list. One thing that Travis gives us for free is isolation:
On Fri, Mar 03, 2017 at 10:48:38PM +0100, Pavel Machek wrote:
Hi!
[auto build test ERROR on linuxtv-media/master]
[also build test ERROR on v4.10 next-20170303]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
Yes, the patch is against Sakar
11 matches
Mail list logo
