Marc Herbert wrote:
> PS: I used NNTP and http://dir.gmane.org/gmane.comp.version-control.git
> to quickly find this old thread (what could we do without NNTP?). Then
> I googled for a web archive of this thread and Google could only find
> this one:
>
On 31/03/16 13:39, Junio C Hamano wrote:
> Andy Lowry writes:
>
>> So I think now that the script should do "update-index --refresh"
>> followed by "diff-index --quiet HEAD". Sound correct?
>
> Yes. That has always been one of the kosher ways for any script to
> make
Andy Lowry writes:
> So I think now that the script should do "update-index --refresh"
> followed by "diff-index --quiet HEAD". Sound correct?
Yes. That has always been one of the kosher ways for any script to
make sure that the files in the working tree that are tracked
OK, great. I think the update-index command is what I need.
If you'll indulge me, I'll describe my use-case in detail, and if you
see anything screwy about it, I'd appreciate feedback. But don't feel
obligated - you've been a great help already.
This is all about publishing updates to a
On Thu, Mar 31, 2016 at 10:12:07AM -0400, Andy Lowry wrote:
> What I'm actually after is a tree-to-filesystem comparison, regardless
> of index. I've currently got a "diff" thrown in as a "work-around"
> before "diff-index", but now I understand it's not a workaround at
> all. If there's a
On Thu, Mar 31, 2016 at 12:39:23PM +, Andy Lowry wrote:
> Following transcript illustrates what I believe to be a bug in git diff-
> index. The session used a git built from latest source, located in
> /tmp/git/git.
>
> 1. New repo, create empty file A, commit changes.
> 2. touch A
> 3. git
On Thu, 2016-03-31 at 12:39 +, Andy Lowry wrote:
> Following transcript illustrates what I believe to be a bug in git
> diff-
> index. The session used a git built from latest source, located in
> /tmp/git/git.
>
> 1. New repo, create empty file A, commit changes.
> 2. touch A
> 3. git
7 matches
Mail list logo