mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Alexander Aring <alex.aring@googlemail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] complete: abstract path complete
Date: Tue, 11 Sep 2012 14:16:44 +0200	[thread overview]
Message-ID: <20120911121644.GJ31207@game.jcrosoft.org> (raw)
In-Reply-To: <CAB_54W69jr4hnoa54mNn76WRCX3BV35UJYb0BrpCqfJUYJ0yOw@mail.gmail.com>

On 12:38 Tue 11 Sep     , Alexander Aring wrote:
>    Hi,
> 
>    I prefer this implementation than the older one, because it check on
>    executable(Maybe we add a attribute for that or check on shebang) file and
>    call found with the full path.
>    I was thinking about to put this as RFC..., because I don't have really a
>    usecase for this.
>    Some commands can do a autocompletion for files that are in $PATH, when
>    this is needed.
> 
>    The naming things, I don't like the name, too. I was doing the naming like
>    the others functions.
>    I will send a v2 with a better name and functionheader
do not like it is not a justification to move or rename it

IT remember the shit that did TI guys on the kernel rename and move stuff
because x or y do notlinke the naming

Best Regards,
J.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-09-11 12:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-11  5:31 [PATCH 1/2] libbb: remove vi tabwidth setting Alexander Aring
2012-09-11  5:31 ` [PATCH 2/2] complete: abstract path complete Alexander Aring
2012-09-11  7:31   ` Sascha Hauer
2012-09-11 10:38     ` Alexander Aring
2012-09-11 12:16       ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2012-09-11  7:21 ` [PATCH 1/2] libbb: remove vi tabwidth setting Sascha Hauer

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=20120911121644.GJ31207@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.com \
    --cc=alex.aring@googlemail.com \
    --cc=barebox@lists.infradead.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