Adam Spiers writes:
Administrivia. Please never deflect direct responses to you with
"Mail-Followup-To" header. I told my mailer to "follow-up" so that I
could give you advice in response, while adding others in the
discussion to Cc so that they do not have to repeat what I said, but
your "Mail
On Mon, Sep 10, 2012 at 6:09 PM, Adam Spiers wrote:
>> > fprintf(stderr, "%s\n", dir->ignored[i]->name);
>> > - fprintf(stderr, _("Use -f if you really want to add
>> > them.\n"));
>> > + fprintf(stderr, _("Use -f if you really want to add them,
On Wed, Sep 05, 2012 at 05:25:25PM +0700, Nguyen Thai Ngoc Duy wrote:
> On Wed, Sep 5, 2012 at 12:26 AM, Junio C Hamano wrote:
> > Nguyen Thai Ngoc Duy writes:
> >
> >>> +static void output_exclude(const char *path, struct exclude *exclude)
> >>> +{
> >>> + char *type = exclude->to_exclude
On Tue, Sep 04, 2012 at 08:06:12PM +0700, Nguyen Thai Ngoc Duy wrote:
> On Sun, Sep 2, 2012 at 7:12 AM, Adam Spiers wrote:
> > --- a/builtin/add.c
> > +++ b/builtin/add.c
> > @@ -273,7 +273,7 @@ static int add_files(struct dir_struct *dir, int flags)
> > fprintf(stderr, _(ignore_er
On Wed, Sep 5, 2012 at 12:26 AM, Junio C Hamano wrote:
> Nguyen Thai Ngoc Duy writes:
>
>>> +static void output_exclude(const char *path, struct exclude *exclude)
>>> +{
>>> + char *type = exclude->to_exclude ? "excluded" : "included";
>>> + char *bang = exclude->to_exclude ? "" : "!"
Nguyen Thai Ngoc Duy writes:
>> +static void output_exclude(const char *path, struct exclude *exclude)
>> +{
>> + char *type = exclude->to_exclude ? "excluded" : "included";
>> + char *bang = exclude->to_exclude ? "" : "!";
>> + char *dir = (exclude->flags & EXC_FLAG_MUSTBEDIR)
On Sun, Sep 2, 2012 at 7:12 AM, Adam Spiers wrote:
> --- a/builtin/add.c
> +++ b/builtin/add.c
> @@ -273,7 +273,7 @@ static int add_files(struct dir_struct *dir, int flags)
> fprintf(stderr, _(ignore_error));
> for (i = 0; i < dir->ignored_nr; i++)
>
On Sun, Sep 2, 2012 at 9:50 PM, Adam Spiers wrote:
> I'm no expert on .gitattributes and check-attr, but AFAICS, all the
> opportunities to share code in the plumbing and front-end seem to be
> taken already, e.g. the directory traversal and path handling. The
> CLI argument parsing is necessaril
Junio C Hamano writes:
> Let's step back a bit and think what this command is about. What is
> the reason why the user wants to run "check-ignore $path" in the
> first place? I think there are two (or three, depending on how you
> count).
>
> (1) You have one (or more) paths at hand. You want
Adam Spiers writes:
> +OPTIONS
> +---
> +--stdin::
> + Read file names from stdin instead of from the command-line.
> +
> +-z::
> + Only meaningful with `--stdin`; paths are separated with a
> + NUL character instead of a linefeed character.
On input, or on output, or both?
The
Adam Spiers writes:
>>> +SYNOPSIS
>>> +
>>> +[verse]
>>> +'git check-ignore' pathname...
>>> +'git check-ignore' --stdin [-z] <
>>
>> Also --quiet option, where check-ignore returns 0 if the given path is
>> ignored, 1 otherwise?
I agree that multiple paths are problematic.
We could er
Hi there,
Firstly, thanks for the quick feedback!
On Sun, Sep 2, 2012 at 11:41 AM, Nguyen Thai Ngoc Duy wrote:
> On Sun, Sep 2, 2012 at 7:12 AM, Adam Spiers wrote:
>> This works in a similar manner to git-check-attr. Some code
>> was reused from add.c by refactoring out into pathspec.c.
>
> Th
On Sun, Sep 2, 2012 at 7:12 AM, Adam Spiers wrote:
> This works in a similar manner to git-check-attr. Some code
> was reused from add.c by refactoring out into pathspec.c.
Thanks, comments from a quick glance. First of all, can we make it
work (or share code) with .gitattributes? We may need to
This works in a similar manner to git-check-attr. Some code
was reused from add.c by refactoring out into pathspec.c.
Thanks to Jeff King and Junio C Hamano for the idea:
http://thread.gmane.org/gmane.comp.version-control.git/108671/focus=108815
Signed-off-by: Adam Spiers
---
.gitignore
14 matches
Mail list logo
