From: Jakub Narebski <jnareb@gmail.com>
To: Wincent Colaiuta <win@wincent.com>
Cc: git mailing list <git@vger.kernel.org>
Subject: Re: "git add" and absolute paths
Date: Mon, 28 Jan 2008 05:08:44 -0800 (PST) [thread overview]
Message-ID: <m33asi9jxp.fsf@localhost.localdomain> (raw)
In-Reply-To: <916BAC14-A5E4-4666-A29E-2CDF114DCD87@wincent.com>
Wincent Colaiuta <win@wincent.com> writes:
> I was somewhat surprised the other day to see that you can't pass
> absolute paths to "git add":
>
[cut]
>
> I understand that you can't add arbitrary paths outside of your
> worktree, but if the absolute path specifies something _inside_ your
> worktree then it seems that this is either a bug or a "usability
> shortcoming" if you prefer to avoid the term "bug".
If I remember correctly this issue was discussed on git mailing list,
and I guess there were even some patches implementing that, but I
don't know what happened iwth them: freeze persiod, troubles with
Cygwin (MS Windows), or what...
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-01-28 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 12:32 "git add" and absolute paths Wincent Colaiuta
2008-01-28 12:43 ` Johannes Schindelin
2008-01-28 13:08 ` Jakub Narebski [this message]
2008-01-28 18:32 ` Jeff King
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=m33asi9jxp.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=win@wincent.com \
/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).