linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Ian Campbell <ijc-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>,
	Dmitry Torokhov
	<dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	Maxime Ripard
	<maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
Cc: devicetree <devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 2/3] devicetree: bindings: use input-event-codes.h for evdev codes
Date: Thu, 17 Sep 2015 15:35:03 -0400	[thread overview]
Message-ID: <55FB15E7.6080502@redhat.com> (raw)
In-Reply-To: <1442487617.18856.177.camel-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>

Hi,

On 09/17/2015 07:00 AM, Ian Campbell wrote:
> On Wed, 2015-09-16 at 15:40 +0100, Ian Campbell wrote:
>>> The intend of the symlink was that the conversion script would copy the target,
>>> rather then follow the symlink. This sorta assumes that there are will be not
>>> symlinks under dt-bindings which link to files inside dt-bindings and thus
>>> should be preserved as symlinks.
>>>
>>> If the copy done in the script will follow the symlink then nothing should
>>> really change for the split DT repo.
>>
>> Interesting idea. I'll see if I can make the conversion routine do that.
>>
>> TBH I have a horrid feeling that this is going to be beyond git rewrite
>> -branch, at least in the mode it is used in today.
>
> It seems that it is possible, after a fashion.
>
> The downside is that either _all_ symlinks (which end up in the output) get
> flattened or some sort of black/whitelisting is needed in the conversion
> scripts themselves (potentially leading to issues or discontinuities) as
> new stuff arrives).
>
> It isn't possible AFAICT tell if a symlink points to something outside of
> the converted set of paths and adjust, at least not without an unreasonable
> amount of overhead on each commit during the rewrite.
>
> Since this new file would be the first symlink in the converted repo I took
> the former approach in my lash up to try it out

Ack, sounds good.

> which was essentially to
> insert the below script into the middle of the "git ls-files | rewrite
> -paths.sed" pipeline which is called by git filter-branch --index-filter.
> Not pretty but it does seem to work.
>
> I want to avoid switching to --tree-filter if at all possible because it
> checks out the tree and is therefore a _little_ I/O intensive ;-)

Thanks for your work on this, so what does this mean for moving forward
with the patch-set I posted. Can this be merged now ? And if not what
are we waiting for ?

Regards,

Hans



>
> Ian.
>
> #!/bin/bash
>
> set -e
>
> while read mode object stage path ; do
>      case "$mode" in
> 	120000)
> 	    # symbolic link
> 	    deref=$(echo $GIT_COMMIT:$path | git cat-file --batch-check='deref-ok %(objectname)' --follow-symlinks)
> 	    case "$deref" in
> 		deref-ok*)
> 		    echo -e "100644 ${deref#deref-ok } $stage\t$path"
> 		    ;;
> 		dangling*) # skip
> 		    ;;
> 		*) # the rest, missing etc
> 		    echo >&2 "Failed to parse symlink $GIT_COMMIT:$path $deref"
> 		    exit 1
> 		    ;;
> 	    esac
> 	    ;;
> 	100*)
> 	    # Regular file, just pass through
> 	    echo -e "$mode $object $stage\t$path"
> 	    ;;
> 	*)
> 	    echo >&2 "Unhandled ls-tree entry: $line"
> 	    exit 1
> 	    ;;
>      esac
> done
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-09-17 19:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-12 13:26 [PATCH 0/3] input / dt-bindings: Unify defining of evdev codes Hans de Goede
2015-09-12 13:26 ` [PATCH 1/3] input: Add an input-event-codes header file Hans de Goede
2015-09-12 13:26 ` [PATCH 2/3] devicetree: bindings: use input-event-codes.h for evdev codes Hans de Goede
2015-09-15 11:24   ` Ian Campbell
2015-09-16 14:27     ` Hans de Goede
2015-09-16 14:40       ` Ian Campbell
2015-09-16 14:43         ` Hans de Goede
2015-09-17 11:00         ` Ian Campbell
     [not found]           ` <1442487617.18856.177.camel-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org>
2015-09-17 19:35             ` Hans de Goede [this message]
2015-09-17 20:00               ` Rob Herring
2015-09-17 20:04                 ` Hans de Goede
     [not found] ` <1442064372-3030-1-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-12 13:26   ` [PATCH 3/3] ARM: dts: sun4i: inet9f-rev03: Add support for game buttons / joysticks Hans de Goede

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55FB15E7.6080502@redhat.com \
    --to=hdegoede-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=ijc-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org \
    --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).