Re: [PATCH v2 10/14] For each exclude pattern, store information about where it came from

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Sep 20, 2012 at 02:31:57PM -0700, Junio C Hamano wrote:
> Adam Spiers <git@xxxxxxxxxxxxxx> writes:
>
> >  void add_exclude(const char *string, const char *base,
> > -		 int baselen, struct exclude_list *el)
> > +		 int baselen, struct exclude_list *el, const char *src, int srcpos)
> >  {
> >  	struct exclude *x;
> >  	size_t len;
> > @@ -341,6 +341,8 @@ void add_exclude(const char *string, const char *base,
> >  	x->base = base;
> >  	x->baselen = baselen;
> >  	x->flags = flags;
> > +	x->src = src;
> > +	x->srcpos = srcpos;
>
> Hrm, don't all elements "x" in "el" share the same "src", even if
> their srcpos may be different?

No not currently - please see the other mail I just sent to the
[PATCH v2 00/14] thread.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]